coderegistry MCP Resources
coderegistry offers 34 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.
-
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 -
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.