project-hub-mcp
Enables pipelines that interact with GitHub, such as opening pull requests from issues.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@project-hub-mcp Run the Issue to PR pipeline on issue #42"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
project-hub-mcp
Run AI agent pipelines from Devin, Claude, and Cursor — via MCP.
Project Hub MCP is a Model Context Protocol server that lets your AI tools run multi-step agent pipelines directly from a conversation.
Built on top of Project Hub — the open-source AI agent pipeline desktop app.
What it does
Once installed, your AI assistant can:
list_pipelines— see all your pipelinesrun_pipeline— execute a pipeline (Issue Analyst → Code Writer → Test Runner → PR Opener)get_run_status— check logs and output of a runlist_agents— see all available agents (Devin, shell, Python, HTTP)run_agent— run a single agent step with any inputcreate_pipeline— define a new pipeline on the flyget_usage— check your monthly run count
Related MCP server: jt-mcp-server
Install
Devin
Add to your Devin MCP settings:
{
"mcpServers": {
"project-hub": {
"command": "npx",
"args": ["-y", "project-hub-mcp"],
"env": {
"PROJECT_HUB_API_KEY": "phub_your_key_here"
}
}
}
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"project-hub": {
"command": "npx",
"args": ["-y", "project-hub-mcp"],
"env": {
"PROJECT_HUB_API_KEY": "phub_your_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"project-hub": {
"command": "npx",
"args": ["-y", "project-hub-mcp"],
"env": {
"PROJECT_HUB_API_KEY": "phub_your_key_here"
}
}
}
}Local mode (no key required)
Set PROJECT_HUB_LOCAL_MODE=1 to run locally with no API key and no run limits:
{
"mcpServers": {
"project-hub": {
"command": "npx",
"args": ["-y", "project-hub-mcp"],
"env": {
"PROJECT_HUB_LOCAL_MODE": "1"
}
}
}
}Usage examples
Once installed, just talk to your AI:
"List my Project Hub pipelines"
"Run the GitHub Issue → PR pipeline with input: Fix the login bug described in issue #42"
"Check the status of run abc-123"
"Run the Code Writer agent on this task: Add dark mode to the settings page"
Environment variables
Variable | Default | Description |
| — | Your API key (get one free at https://projecthub.dev/api-key) |
|
| Set to |
|
| Directory where agents, pipelines, and run history are stored |
| — | Default Devin model (e.g. |
|
| Devin permission mode: |
|
| Default working directory for Devin agent runs |
Pricing
Plan | Price | Runs/month |
Free | £0 | 10 |
Pro | £19/mo | Unlimited |
Get your free API key: https://projecthub.dev/api-key
Run from source
git clone https://github.com/atikahjapry/project-hub-mcp
cd project-hub-mcp
npm install
npm run build
# Run in local mode (no key, no limits)
PROJECT_HUB_LOCAL_MODE=1 node dist/index.jsSecurity
Data stored locally
Agents, pipelines, and run history are stored in ~/.project-hub-mcp/store.json on your own machine. The directory is created with mode 0700 and the file with mode 0600 — readable only by your user account.
API keys are hashed with SHA-256 before being stored. The raw key is never written to disk.
Secrets in envVars
When creating a shell or Python agent, the envVars field sets environment variables for the spawned process. Use $VARIABLE_NAME references, not literal values — the reference is stored, and the real value is resolved from your shell environment at runtime and never written to disk.
// Bad — literal token stored in store.json in plaintext
{ "GITHUB_TOKEN": "ghp_actualtoken123" }
// Good — reference stored; real value read from host env at runtime
{ "GITHUB_TOKEN": "$GITHUB_TOKEN" }The server enforces this: saveAgent will throw if it detects a known secret pattern (GitHub tokens, OpenAI keys, AWS keys, long hex strings, etc.) in an envVars value. If you try to save such an agent you will get a clear error pointing to the offending key and showing the correct $REF form.
Put real secrets in your shell profile (~/.bashrc, ~/.zshrc) or your MCP host's env config block, then reference them by name.
Shell commands
Shell and Python agents run bash -c <your-command>. The user input passed to the agent is not interpolated into the command string — it is passed via the AGENT_INPUT environment variable to prevent shell injection.
Reference it in your command like this:
# Access user input safely via $AGENT_INPUT
echo "$AGENT_INPUT" | some-toolLogs
All stdout/stderr captured during agent runs is scrubbed for common secret patterns (token=, password=, Bearer, etc.) before being stored. If you need to ensure sensitive output is never logged, set outputParser: "last_line" or "json_field" on the agent to capture only structured output.
How it works
Agents and pipelines are stored locally in
~/.project-hub-mcp/store.jsonThe server runs via stdio — your AI tool spawns it as a subprocess
Devin agents call the
devinCLI — you need Devin installed (https://devin.ai/download)Shell agents run via
bash -c; user input passed viaAGENT_INPUTenv var (never interpolated into the command)All run logs and outputs are persisted locally with secret scrubbing applied
Related
Project Hub desktop app — the full GUI for building and running pipelines
Project Hub landing page — marketing site and agent marketplace
MIT License · Built by Atikah Japry
Available Tools
7 toolscreate_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.
Inputs: name (required), description (required), agent_ids (required), api_key.
get_run_statusB
Get the current status and full logs of a pipeline run by its run ID.
Inputs: run_id (required).
get_usageB
Check how many pipeline runs you've used this month and what plan you're on.
Inputs: api_key.
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.
Inputs: no named parameters.
list_pipelinesA
List all available AI agent pipelines. Shows name, description, trigger type, and number of agents in each pipeline.
Inputs: no named parameters.
run_agentA
Run a single agent with a given input. Useful for quick one-off tasks without a full pipeline.
Inputs: agent_id (required), input (required), api_key.
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.
Inputs: pipeline_id (required), input (required), api_key.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows a planning agent to delegate tasks to executor agents (e.g., Claude Code, Aider) with bi-directional communication and real-time log streaming.46 npm15AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.79 npm10MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.61MIT