Spidergate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Yes | GitHub Personal Access Token with repo scope or fine-grained permissions. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_upcoming_calendar_eventsA | Retrieves upcoming events across all active Google Calendars within the next X days. |
| add_calendar_eventB | Creates a new calendar event.
|
| delete_calendar_eventB | Deletes a calendar event by its ID, with automatic scan fallback. |
| list_google_tasksB | Lists tasks from the primary task list including status and ID. |
| add_google_taskB | Creates a new Google Task. due_iso in RFC3339 format (e.g. '2026-08-12T00:00:00.000Z'). |
| complete_google_taskB | Marks a Google Task as completed using its Task ID. |
| delete_google_taskB | Deletes a Google Task by its Task ID. |
| list_github_issuesA | Lists issues for a given repository (e.g. 'owner/repo'). State: 'open', 'closed', 'all'. |
| create_github_issueC | Creates a new issue in a GitHub repository. |
| comment_github_issueA | Adds a comment to an existing issue or pull request. |
| list_github_pull_requestsB | Lists pull requests for a given repository. |
| create_github_pull_requestB | Creates a new pull request. |
| commit_and_push_fileC | Creates or updates a file directly in a GitHub repository. |
| get_spidergate_statusA | Returns runtime diagnostics and status metadata for the gateway. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.