Portfolio Monitoring — coderegistry MCP Resource
Portfolio Monitoring
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 Portfolio Monitoring from your client
- Claude Code coderegistry Resource/Portfolio Monitoring run in your project directory
- Claude Desktop coderegistry Resource/Portfolio Monitoring ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor coderegistry Resource/Portfolio Monitoring ~/.cursor/mcp.json
- VS Code coderegistry Resource/Portfolio Monitoring .vscode/mcp.json
- Zed coderegistry Resource/Portfolio Monitoring ~/.config/zed/settings.json
- Windsurf coderegistry Resource/Portfolio Monitoring ~/.codeium/windsurf/mcp_config.json
- Cline coderegistry Resource/Portfolio Monitoring ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI coderegistry Resource/Portfolio Monitoring ~/.gemini/settings.json
- Grok coderegistry Resource/Portfolio Monitoring .mcp.json (in your project root)
- ChatGPT coderegistry Resource/Portfolio Monitoring Settings → Connectors → Advanced → Developer mode
- Claude.ai coderegistry Resource/Portfolio Monitoring Settings → Connectors → Add custom connector
- LangChain coderegistry Resource/Portfolio Monitoring 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
- 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
- Cursor 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.