founden-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOUNDEN_API_KEY | Yes | Your Founden API key (starts with omk_) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_companyB | Start a Founden build from a plain-language prompt. Cost: 1 credit. |
| get_buildA | Get build status and the live preview URL. Cost: 0 credits. |
| message_buildA | Send a follow-up instruction to a running build. Cost: 0 credits. |
| stop_buildA | Stop a running build. Cost: 0 credits. |
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 4 tools
Each tool has a clearly distinct purpose: starting a build, retrieving status, sending follow-up instructions, and stopping. No overlap in functionality.
All names use snake_case and imperative verbs, but 'build_company' uses a different noun ('company') than the others ('build'), breaking the pattern slightly.
With 4 tools covering creation, status, messaging, and control, the count is well-scoped for a build service without unnecessary complexity.
Core lifecycle (create, read, update via messages, delete via stop) is covered. Minor gaps like listing builds or history are absent but not critical for basic usage.