code-synapse
Server Details
Finds real, maintained open-source repos that fit your project. MCP grounding for coding agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 2 of 2 tools scored.
Both tools serve essentially the same purpose, with 'search_components' explicitly listed as a deprecated alias of 'find_fit_candidates'. This creates clear overlap and potential confusion for an agent deciding which to use.
Both names use snake_case and follow a verb_noun pattern ('find_fit_candidates' and 'search_components'), which is consistent. The slight difference in specificity does not break consistency.
With only two tools and one deprecated, the effective tool count is one. This is too few for a meaningful server, making the surface feel thin and underdeveloped.
The server provides only search functionality for open-source reuse decisions. There are no tools for detailed inspection, comparison, or post-adoption actions, leaving significant gaps for a complete workflow.
Available Tools
2 toolsfind_fit_candidatesInspect
Pre-adoption decision tool for open-source reuse. Call BEFORE implementing non-trivial functionality that a maintained OSS component could provide (queue, scheduler, parser, auth, cache, protocol client, ...) or before adding a dependency. Send a short capability need plus your project's minimal constraints; returns up to 12 candidates by default (up to 20 when max_candidates is provided), with per-constraint pass/fail/unknown, evidence basis (observed vs inferred), and explicit no-hit semantics.
| Name | Required | Description | Default |
|---|---|---|---|
| need | Yes | Capability need, e.g. "job queue with retry for node.js". No project names, paths, or secrets. | |
| strict | No | also exclude candidates whose required constraint fields are unknown | |
| telemetry | No | aggregate stores zero user text (outcome counters only); debug also stores the need for 30 days | aggregate |
| exclusions | No | ||
| constraints | No | Minimal project constraints. Each verdict comes back as pass|fail|unknown per candidate. | |
| max_candidates | No | ||
| existing_components | No | owner/repo you already use — excluded and counted as already_have |
Output Schema
| Name | Required | Description |
|---|---|---|
| corpus | Yes | |
| outcome | Yes | |
| candidates | Yes | |
| relaxation | No | present on constrained_out: real recount when dropping one constraint |
| no_hit_guidance | No | |
| contract_version | Yes | |
| rejected_summary | Yes |
search_componentsInspect
Deprecated alias of find_fit_candidates (kept for compatibility; free-text search without constraint checking). Search open-source components in the Code Synapse graph by keyword, role, or category. Returns candidates with signals (role, protocols, affordance, fit, freshness). fit.status="unknown" means fit fields are not yet extracted — verify runtime/interfaces via the README before relying on them.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | e.g. "music server", "vector db", "scraping" |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!