project-hub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVIN_MODEL | No | Default Devin model (e.g., claude-sonnet-4) | |
| PROJECT_HUB_DATA | No | Directory for storing agents, pipelines, and run history | ~/.project-hub-mcp |
| DEVIN_WORKING_DIR | No | Default working directory for Devin agent runs | $HOME |
| PROJECT_HUB_API_KEY | No | Your API key from projecthub.dev | |
| DEVIN_PERMISSION_MODE | No | Devin permission mode: auto, smart, or dangerous | auto |
| PROJECT_HUB_LOCAL_MODE | No | Set to '1' for unlimited local runs without API key | 0 |
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_pipelinesA | List all available AI agent pipelines. Shows name, description, trigger type, and number of agents in each pipeline. |
| run_pipelineA | Execute an AI agent pipeline with an initial input. The pipeline will run each agent in sequence, passing output between them. Returns a run ID you can use to check status. |
| get_run_statusB | Get the current status and full logs of a pipeline run by its run ID. |
| list_agentsB | List all available agents. Each agent is a single execution unit: a Devin AI session, shell script, Python script, or HTTP API call. |
| run_agentA | Run a single agent with a given input. Useful for quick one-off tasks without a full pipeline. |
| create_pipelineA | Create a new pipeline by specifying an ordered list of agent IDs. Agents run in sequence, each receiving the previous agent's output as input. |
| get_usageB | Check how many pipeline runs you've used this month and what plan you're on. |
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 7 tools
All 7 tools have clearly distinct purposes: creating vs running pipelines, running a single agent, checking run status, checking usage, and listing agents/pipelines. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_pipeline, get_run_status, list_agents). No deviations or mixed conventions.
7 tools is appropriate for the server's purpose of managing pipeline runs and agents. Each tool serves a distinct function without excess or deficiency.
The tool set covers the core lifecycle: create, run, monitor (status), list, and usage check. Minor gaps exist, such as missing update/delete for pipelines or agent management, but the surface is sufficient for common workflows.