Spidergate MCP
# Spiderweb MCP
[](https://opensource.org/licenses/MIT)
[](https://www.python.org/)
[](https://github.com/jlowin/fastmcp)
[](https://astral.sh/uv)
**Spiderweb MCP** is a host-native Model Context Protocol (MCP) gateway connecting LLM agents (Claude Code, Hermes Agent) with personal productivity tools: **Google Workspace (Calendar & Tasks)**, **GitHub**, and **SearXNG Search**.
Executed natively via `uv` over standard I/O (`stdio`).
---
## Features
- **Google Calendar:** Multi-calendar scans (primary, shared, family), event creation, fuzzy calendar matching, and deletion.
- **Google Tasks:** Full CRUD operations (list, create, complete, delete).
- **GitHub API Suite:** Manage issues, PRs, file commits, and branch inspections via PyGithub.
- **Local Web Search:** Private search queries routed through a local SearXNG instance.
- **Host-Native Execution:** Managed directly by `uv`—no container wrappers, zero runtime port conflicts.
## Project Structure
```text
spiderweb-mcp/
├── auth/ # OAuth tokens & credentials.json (gitignored)
├── src/
│ └── spiderweb_mcp/
│ ├── auth/ # OAuth2 handlers and token refresh
│ ├── tools/ # Modular tool definitions (Calendar, Tasks, GitHub, SearXNG)
│ └── server.py # FastMCP stdio gateway
├── .env.example
├── pyproject.toml
├── uv.lock
└── README.md
TDQS
Scored across 14 tools
Each tool targets a distinct resource and action: calendar events, Google Tasks, GitHub issues/PRs, and gateway status. Within each domain, verbs like list, add, delete, complete, and comment clearly separate operations, leaving no ambiguity.
Most tools follow a verb_noun pattern (e.g., list_github_issues, delete_google_task), but there are minor inconsistencies: 'add' is used for calendar events and tasks while 'create' is used for GitHub issues/PRs, and 'get_upcoming' mixes with 'list_*'. Still, the overall pattern is readable and predictable.
With 14 tools spanning three distinct service integrations plus a status diagnostic, the count feels well-scoped. Each tool earns its place, and the number is neither bloated nor thin.
Core workflows are covered: calendar events support create/read/delete, tasks support create/read/complete/delete, and GitHub supports issues/PRs listing, creation, commenting, and file commits. Missing update operations (e.g., update event, update task, merge PR) are minor gaps that agents can work around.