obox-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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| just_project_runnerB | Finalizes project setup by detecting structure. Call this tool immediately after creating any new project. |
| obox_fastapi_init_projectA | Initializes a new FastAPI project at the specified path. Sets up uv environment with the specified Python version and installs fastapi[standard]. Args: path: The absolute path where the project should be initialized. python_version: The Python version to use (default: "3.12"). |
| react_init_projectA | Initializes a new React project at the specified path. Setup includes:
Args: path: The absolute path where the project should be initialized. |
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 3 tools
Each tool has a clearly distinct purpose: one initializes FastAPI, one initializes React, and one finalizes any newly created project. There is no functional overlap between them.
The two initialization tools follow a similar pattern (framework_init_project), but the finalizer tool (just_project_runner) uses a completely different naming style. Additionally, one tool has the 'obox_' prefix while the other does not, causing inconsistency.
Three tools is a well-scoped count for a project scaffolding server. Each tool serves a distinct purpose and the count is within the ideal 3-15 range.
The tool set covers the init and finalize lifecycle for FastAPI and React, but lacks support for other common frameworks and has no additional operations like listing projects or managing dependencies. The finalizer is somewhat disconnected from the init tools, requiring manual invocation.