Cursor Setup — coderegistry MCP Resource
Cursor Setup
is one of 34 resources on the
coderegistry
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Cursor Setup from your client
- Claude Code coderegistry Resource/Cursor Setup run in your project directory
- Claude Desktop coderegistry Resource/Cursor Setup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor coderegistry Resource/Cursor Setup ~/.cursor/mcp.json
- VS Code coderegistry Resource/Cursor Setup .vscode/mcp.json
- Zed coderegistry Resource/Cursor Setup ~/.config/zed/settings.json
- Windsurf coderegistry Resource/Cursor Setup ~/.codeium/windsurf/mcp_config.json
- Cline coderegistry Resource/Cursor Setup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI coderegistry Resource/Cursor Setup ~/.gemini/settings.json
- Grok coderegistry Resource/Cursor Setup .mcp.json (in your project root)
- ChatGPT coderegistry Resource/Cursor Setup Settings → Connectors → Advanced → Developer mode
- Claude.ai coderegistry Resource/Cursor Setup Settings → Connectors → Add custom connector
- LangChain coderegistry Resource/Cursor Setup pip install langchain-mcp-adapters
Other resources on this server
- Docs Index
- AGENTS.md
- The Code Registry MCP Server
- Changelog
- LICENSE
- MCP API Reference
- Architecture - Source Code Types
- Authentication
- Facet Glossary
- Getting Started
- Response Schemas
- Troubleshooting
- GitHub Integration Workflow
- Local Repo Analysis Workflow
- Multi-Project Setup
- M&A Due Diligence with Claude
- Portfolio Monitoring
- Security Audit
- Tech Debt Analysis
- Analyze code on every PR
- GitLab CI example
- jenkins-pipeline
- Claude API Integration
- Example of using Code Registry MCP via Claude API
- typescript-example
- Claude Desktop Setup
- config
- Cline (VS Code) Setup
- Custom MCP Clients
- nodejs-client
- python-client
- api-responses
- mcp-tools
coderegistry also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.