solodot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | No | Supabase project URL (required for remote HTTP mode). | |
| VERTEX_API_KEY | No | API key for Vertex AI. | |
| SOLODOT_MCP_PORT | No | Port for HTTP server (optional, default 8787). | |
| ANTHROPIC_API_KEY | No | API key for Anthropic. | |
| SUPABASE_SECRET_KEY | No | Supabase secret key (required for remote HTTP mode). | |
| SOLODOT_MCP_API_KEYS | No | Bearer token for HTTP mode authentication. | |
| SOLODOT_MCP_ENV_FILE | No | Absolute path to .env file for container run (optional). | |
| SOLODOT_DEFAULT_PROVIDER | No | The default AI provider, either 'anthropic' or 'vertex'. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| route_painpointB | Diagnose the active solo-founder painpoint, select exactly one Solodot execution pack, and return a lightweight action preview. This does not perform external actions. |
| generate_execution_assetA | Generate one concrete, preview-only execution asset for the pack already selected by route_painpoint. The routed pack cannot be changed by this tool. |
| review_execution_assetA | Record approve, revise, or reject for a generated Solodot asset. Approval records acceptance only and never executes the asset externally. |
| get_solodot_runA | Return the authenticated founder's diagnosis, generated assets, approval history, and latest recommended step. |
| export_solodot_runA | Return an approved execution asset as Markdown or JSON. The tool returns content only; it does not write files, post messages, or publish. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| execution-packs | The six workflows available to the painpoint router. |
| approval-boundaries | Actions that Solodot must never perform silently. |
| product-context | The product promise and role of the intake/router. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ozgureyilmaz/solodot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server