Gyst MCP
Enables listing and updating clients, projects, and tickets from your editor via Gyst's API.
README
Gyst MCP
Standalone Cursor MCP server for Gyst — list and update clients, projects, and tickets from your editor.
Quick start
-
Generate a token in Gyst → Settings → Cursor MCP.
-
Clone and build this repo:
git clone https://github.com/NathanHartkopf/gyst-mcp.git cd gyst-mcp npm install && npm run build -
Add to
~/.cursor/mcp.json:{ "mcpServers": { "gyst": { "command": "node", "args": ["/absolute/path/to/gyst-mcp/dist/index.js"], "env": { "GYST_API_URL": "https://gyst.nathanh.app", "GYST_API_TOKEN": "gyst_your_token_here", "GYST_WORKSPACE": "/absolute/path/to/your/repo" } } } }GYST_API_TOKEN— personal token from Gyst Settings (scopes access to your account only)GYST_API_URL— your Gyst deployment URL (defaults to production if omitted in code)GYST_WORKSPACE— optional; helpsget_projects_for_current_repowhen Cursor does not expose workspace roots
-
Restart Cursor to load the MCP server.
Legacy direct-KV mode
For local development against Vercel KV directly (not recommended for end users):
vercel env pull .env.mcp --environment=production --yes
Configure with GYST_ENV_FILE, KV_REST_API_URL, KV_REST_API_TOKEN, and ADMIN_EMAIL instead of GYST_API_TOKEN.
Tools
| Tool | Description |
|---|---|
list_clients |
List all clients (summary) |
get_client |
Full client details by ID |
list_projects |
List projects, optional clientId filter |
get_project |
Full project details by ID |
get_projects_for_current_repo |
Projects linked to the workspace GitHub repo |
list_tickets |
List tickets; optional filters |
get_ticket |
Full ticket details by ID |
get_ticket_by_key |
Full ticket details by key (e.g. GYST-4) |
create_ticket |
Create a ticket with auto-assigned key |
update_ticket |
Update ticket fields |
update_project |
Update project fields |
update_project_ticket_statuses |
Set a project's ticket status list |
update_ticket_status |
Change a ticket's status |
add_project_ai_dev_comment |
Post an AI Dev comment on a project |
add_ticket_ai_dev_comment |
Post an AI Dev comment on a ticket |
sync_ticket_dev_links |
Scan GitHub repos for commits/PRs matching a ticket key |
Sample skill
See skills/complete-new-work/SKILL.md for a Cursor agent skill that discovers open tickets, asks for confirmation, and runs the full delivery workflow.
Development
npm run build
node scripts/test-mcp-tool.mjs
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.