MCP Server for Cursor Integration

@knyengera

Repository

Basic information

About MCP Server for Cursor Integration

No overview available yet

#mcp-server #cursor-integration#coda-api

MCP Server for Cursor Integration config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

MCP Server for Cursor Integration tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server for Cursor Integration?

A Managed Context Provider (MCP) server that integrates Cursor (the AI coding assistant) with Coda.io documentation. It fetches context from Coda.io tables to provide relevant, context-aware responses within Cursor.

How to use MCP Server for Cursor Integration?

Install Node.js (v14+), clone the repository, run npm install, configure a .env file with your Coda.io API token and document ID. Start the server with npm run dev (development) or npm start (production). Use ngrok (ngrok http 3000) to expose it publicly, then update your MCP client configuration (mcp.json) with the provided ngrok URL and the /context endpoint.

Key features of MCP Server for Cursor Integration

Connects Cursor to Coda.io documentation via API
Built-in caching for faster repeated queries
RESTful API endpoints for context and health
Supports multiple Coda.io tables simultaneously
Includes health check and cache management endpoints

Use cases of MCP Server for Cursor Integration

Query Jira ticket details stored in Coda.io directly from Cursor
Retrieve API documentation snippets without leaving the editor
Access architecture decision records while coding
Combine documentation from several Coda tables into one response

Frequently asked questions

What does this server do?

It acts as a middleware between Cursor and your Coda.io documentation tables, fetching and returning relevant context based on search queries.

What are the prerequisites?

You need Node.js v14 or higher, a Coda.io account with API access, and a Coda.io document that contains the required tables (Jira Tickets, API Documentation, Architecture Decisions).

How do I expose the server to the internet?

Use ngrok: install it globally (`npm install -g ngrok`), run `ngrok http 3000` while the server is running, and update the `url` in your `mcp.json` file with the ngrok‑provided URL.

How do I manage the cache?

Send a POST request to `/cache/clear` to clear all cache, or a GET request to `/cache/stats` to view cache statistics.

Which tables does the server expect in Coda.io?

By default it looks for “Jira Tickets”, “API Documentation”, and “Architecture Decisions”. You can change these table names in `src/services/mcp.service.js`.

Comments

More Developer Tools MCP servers

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Vibgrate MCP

Vibgrate

Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Testiny MCP server

Mategra GmbH

Testiny is a test case management platform. Its remote MCP server lets AI assistants such as Claude, ChatGPT, GitHub Copilot, Cursor and other MCP clients work directly with your Testiny data. Browse and search projects,

OrangePro

Aamir Siddiqui

OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Yocoolab

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools