Seed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEED_ORG | No | Organization name for login authentication | |
| SEED_EMAIL | No | Email for login authentication | |
| SEED_API_BASE | Yes | Base URL for the Seed API (default: http://localhost:3007) | |
| SEED_PASSWORD | No | Password for login authentication | |
| SEED_ACCESS_TOKEN | No | Access token for API authentication | |
| SEED_MAINT_PASSWORD | No | Maint password for organization listing | |
| SEED_MAINT_ACCESS_TOKEN | No | Maint access token for organization listing |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| seed_get_access_tokenA | Get a Seed API access token by prompting for credentials through the MCP client. |
| seed_list_orgsB | List registered Seed organizations. Requires SEED_MAINT_ACCESS_TOKEN or SEED_MAINT_PASSWORD. |
| seed_register_orgB | Register a new Seed organization with backend defaults. This calls the public organization register endpoint. |
| seed_create_orgA | Create a Seed organization with optional organization metadata. Requires the configured Seed user to have create access. |
| seed_update_orgC | Update Seed organization metadata by organization name. Requires the configured Seed user to have update access. |
| seed_delete_orgA | Delete a Seed organization by name, including its organization database file when present. Requires delete access. |
| seed_list_tablesA | List Seed table metadata from the configured organization. |
| seed_get_tableC | Get Seed metadata for one table. |
| seed_create_tableB | Create a Seed table with fields and optional relationships. |
| seed_add_relationshipB | Add or replace a relationship on an existing Seed table. |
| seed_list_framesC | List Seed frame metadata from the configured organization. |
| seed_get_frameB | Get Seed metadata for one frame. |
| seed_create_frameA | Create a Seed frame on an existing table. Frames select table fields/relations and optional filters before creating views. |
| seed_update_frameB | Update Seed frame metadata by frame name. |
| seed_delete_framesA | Delete Seed frames by name. |
| seed_list_viewsB | List Seed view metadata from the configured organization. |
| seed_get_viewA | Get Seed metadata for one view. |
| seed_create_viewB | Create a Seed view on an existing frame. |
| seed_update_viewB | Update Seed view metadata by view name. |
| seed_delete_viewsB | Delete Seed views by name. |
| seed_list_documentsA | List documents from a Seed table. Useful for finding record ids before creating related data. |
| seed_add_documentsA | Add exact Seed document payloads to a table. Use this when rows include relations. |
| seed_add_mock_dataA | Add simple mock rows to a Seed table. Each row is treated as field values only; use seed_add_documents for relations. |
| seed_delete_documentsA | Delete documents from a Seed table by id. Useful for cleaning up mock data. |
| seed_grant_permissionA | Grant a role access to a Seed resource by creating a permissions row and linking it to the role. Access bitmask: create=1, read=2, update=4, delete=8, full CRUD=15. |
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 25 tools
Most tools are clearly distinct by resource and action, but there is some overlap between seed_register_org and seed_create_org, as well as between seed_add_documents and seed_add_mock_data. The descriptions help differentiate them, but an agent could still confuse the subtly different purposes.
All tools follow a consistent seed_<verb>_<noun> snake_case pattern. The verbs are predictable (list, get, create, update, delete, add) and the nouns correspond to resources. Minor pluralization differences (e.g., delete_frames vs delete_org) do not break the overall pattern.
With 25 tools, the server is at the upper boundary of the typical range, but the count is justified by covering multiple resources (orgs, tables, frames, views, documents, permissions). A few tools could be consolidated without loss of clarity, but the scope is still reasonable.
The tool surface has notable gaps: tables lack update and delete operations, documents lack update and get-by-id, and permissions only support grant without revoke. While the core workflows for frames and views are fully covered, these missing operations will require workarounds and may cause agent failures in common scenarios.