CoderSwap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to 'true' for detailed logging (optional) | |
| CODERSWAP_API_KEY | Yes | Your CoderSwap API key (required) | |
| CODERSWAP_BASE_URL | No | The base URL for the CoderSwap API | http://localhost:8000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coderswap_create_projectB | Create a new vector search project in CoderSwap |
| coderswap_list_projectsB | List all CoderSwap projects available to your API key |
| coderswap_get_project_statsC | Get statistics and information about a specific project |
| coderswap_research_ingestC | Submit research summary and URLs for web crawling, chunking, embedding, and optional DSL generation |
| coderswap_get_job_statusB | Check the status of a research ingestion job |
| coderswap_searchC | Execute a hybrid search query against a CoderSwap project using DSL-powered ranking |
| coderswap_validate_searchB | Run validation queries to test search quality and coverage (non-DSL quality check) |
| coderswap_log_session_noteC | Record lightweight ingestion summary for session continuity (non-DSL) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of the workflow: project management (create, list, get stats), job monitoring (get job status), ingestion (research_ingest, log_session_note), and search operations (search, validate_search). There is no overlap in functionality that would cause misselection.
All tools follow a consistent 'coderswap_verb_noun' pattern throughout, using snake_case uniformly. The verbs are descriptive and appropriate for each action (e.g., create_project, get_job_status, list_projects), making the naming highly predictable and readable.
With 8 tools, the count is well-scoped for a vector search project management server. Each tool earns its place by covering essential operations: project lifecycle (create, list, get stats), ingestion workflows (research_ingest, log_session_note), job monitoring, and search functionality (search, validate). This is neither too sparse nor bloated.
The tool set provides comprehensive coverage for core CoderSwap workflows, including project CRUD, ingestion, and search. A minor gap exists in the lack of update or delete operations for projects, which might limit full lifecycle management, but agents can likely work around this given the server's focus on ingestion and search.