3vilTid

Tid MCP Agents — AI skill for Claude Code

AI community

🏦 Universal AI Agent & Skill Vault.

How to install Tid MCP Agents

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 3vilTid/Tid-MCP-Agents and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Tid MCP Agents does

🏦 Universal AI Agent & Skill Vault. Custom bank of modular skills & agent blueprints built on MCP. Fully decoupled from AI providers: connect instantly to Claude, GPT, Gemini, or run 100% offline via Ollama (Llama 3.1 70B) on local hardware. Future-proof automation engine ready for cloud or edge computing.

Alternatives in AI

Claudian — An Obsidian plugin that embeds Claude Code as an AI collaborator in your vault 7.7k ★
Osaurus — Own your AI. The native macOS harness for AI agents -- any model, persistent memory, autonomous execution, cry 5.1k ★
Cc Mirror — Create multiple isolated Claude Code variants with custom providers (Z.ai, MiniMax, OpenRouter, LiteLLM) 2.1k ★

README

MCP Google Sheets Connector

A [Model Context Protocol](https://modelcontextprotocol.io) server that gives Claude **direct read/write access to a Google Sheet** — no more downloading an Excel file, editing it, and re-uploading it by hand.

It was built for Indonesia Quest's `CLAUDE TEMPLATE OPERATIONAL ROADBOOK` sheet (spreadsheet ID `1tAwfwkjWd98iC2WZWkhRUR_WO0QRC6mdWUCzDHfoKS8`, tab `OPERATIONAL ROADBOOK`), but it works against any Google Sheet the configured service account has been granted edit access to.

Quickstart: set this up from scratch on a new machine

This is the exact sequence to go from nothing to a working connector on a brand new computer, under a different Claude account — no assumed prior setup. It deploys to **Cloudflare Workers** (Option D below), because it's the only path here that needs no credit card at all. If you'd rather use Google Cloud Run, Claude Desktop, or a Claude Code/Cowork session tied to this repo instead, skip to [Setup](#setup) → step 4 for those options; steps 1–3 below (Node.js, the Google service account, cloning the repo) are the same regardless of which option you pick.

**1. Install prerequisites**

Node.js: download the LTS installer from nodejs.org and run it, keeping the defaults (you don't need the optional "Tools for Native Modules" step — leave that checkbox unticked). Close and reopen your terminal afterwards.
- Windows only: if npm --version then fails with "running scripts is disabled on this system", PowerShell is blocking npm's own script. Fix it once with (this only affects your user account, not the whole system):
```
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
```
git: usually already installed (check with git --version); if not, get it from git-scm.com.