Scribe MCP Server for CursorGive Cursor instant access to 10 tools to Check Scribe Status, Get Documentation Stats, Get Recent Documents, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Scribe app connector for Cursor is a standout in the Productivity category — giving your AI agent 10 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Scribe and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"scribe": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Scribe MCP Server
Connect your Scribe organization to any AI agent and access your process documentation library through natural conversation.
Cursor's Agent mode turns Scribe into an in-editor superpower. Ask Cursor to generate code using live data from Scribe and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Full Search — Search across all Scribes and Knowledge Pages simultaneously.
- Filtered Search — Search only guides or only pages for targeted results.
- Team Scoping — Find documents within a specific team for departmental queries.
- Date Filtering — Search by creation date range or get recent documents.
- Teams — List all teams and their documents for content auditing.
- Statistics — Get an overview of your documentation footprint.
The Scribe MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 10 Scribe tools available for Cursor
When Cursor connects to Scribe through Vinkius, your AI agent gets direct access to every tool listed below — spanning scribe, process-documentation, knowledge-base, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Verify Scribe API connectivity
Get documentation statistics
Get documents created in the last 30 days
Useful for auditing team documentation. Get all documents for a specific team
List all teams in your Scribe organization
Dates should be in YYYY-MM-DD format. Search documents by creation date range
Search documents within a specific team
Search across all Scribes and Pages
Search only Knowledge Pages
Search only Scribe guides
Connect Scribe to Cursor via MCP
Follow these steps to wire Scribe into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Scribe
Why Use Cursor with the Scribe MCP Server
Cursor AI Code Editor provides unique advantages when paired with Scribe through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Scribe + Cursor Use Cases
Practical scenarios where Cursor combined with the Scribe MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Scribe in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Scribe immediately.
"Search for all documentation about 'onboarding'."
"List all teams in our Scribe organization."
"What documents were created in the last 30 days?"
Troubleshooting Scribe MCP Server with Cursor
Common issues when connecting Scribe to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Scribe + Cursor FAQ
Common questions about integrating Scribe MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.