M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionRLM Tools BSL MCP ServerToken-efficient analysis MCP server for 1C (BSL) codebasesGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS60 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions9 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • 1C:Enterprise projects with CF, EDT, or MDO source formats
  • Large configurations with 20K+ files that cannot fit into a single session context
  • Deterministic codebase questions, e.g. finding an HTTP service and its methods or how a document posting routine works
  • Teams that want to save context and tokens and avoid maintaining RAG infrastructure
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Scenarios needing a complete dependency graph of all configuration objects (requires a pre-indexed RAG/graph MCP)
  • Semantic/embedding search over object descriptions
  • Vague, non-deterministic questions like 'how does budgeting work in ERP' or 'how do cellular warehouses work in UT', which need full RAG or a strong model to turn them into strict queries
  • Treating it as an official 1C product: it is not maintained by 1C
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Read 1C source directories (BSL files, XML/MDO descriptions, metadata)
  • Write and manage SQLite index files on the host
  • Read and modify the projects.json registry next to the server directory (mutating operations require a password)
  • Execute agent-submitted Python scripts inside a sandbox
  • Optional access to an LLM endpoint (OpenAI-compatible OpenRouter, Ollama, vLLM, or the Anthropic API), only when llm_query is configured
  • Optional use of Git on the host to read the source repository (enables git_search)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Agent-submitted Python scripts are executed in a sandbox whose real strength determines the host's exposure surface
  • A .git directory in the sources automatically enables git grep full-text search over all files, which may surface 'raw' XML/MDO and text content developers did not expect to expose
  • When llm_query is configured, script content or code fragments may be sent to an external LLM endpoint
  • The registry password protects mutating operations to stop the AI acting without confirmation, but it is not strong encryption or isolation
  • Indexing is slow on HDDs or network shares, and indexes persist code content read from disk
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Kilo Code, Roo Code, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615