Main Street MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_industriesA | Lists the industry starter kits this server can generate. Use this first, then pass the chosen id to create_business_config. |
| create_business_configA | Writes a starter business.yaml for the chosen industry into the folder this server was pointed at. Refuses to overwrite an existing file. After this, edit the file with the owner's real details and have them reconnect the extension. |
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 2 tools
The two tools have clearly distinct roles: list_industries enumerates the available starter kits, and create_business_config generates the file from a chosen kit. There is no overlap, and the intended workflow dependency is explicitly documented.
Both tool names follow the same verb_noun pattern (list_industries, create_business_config). The naming is consistent, predictable, and accurately describes each action.
Two tools is on the thin side, but it is reasonable for a narrowly scoped server whose purpose is listing starter industries and generating one config file. Each tool earns its place, and adding more would likely go beyond the stated design.
The tool set covers the promised flow: discover an industry starter and create the corresponding business config, with a clear manual-editing handoff afterward. It intentionally omits update/overwrite behavior because the server explicitly refuses to overwrite existing files.