MCP

ShipFoundry MCP lets a user-owned coding agent list relevant updates, fetch current project context, retrieve the appropriate brief or task packet, and record outcomes without requiring Linear or GitHub write access.

When To Use This

Use MCP when your coding agent should pull ShipFoundry context directly into the local development workflow.

MCP is the best path when the agent will inspect the repo itself, compare ShipFoundry evidence with local state, and report a bounded outcome back.

How It Works

The default endpoint is:

{APP_URL}/mcp

Use the endpoint shown in /dashboard/settings/mcp. Production environments can expose a configured MCP URL through NEXT_PUBLIC_SHIPFOUNDRY_MCP_URL.

OAuth is the primary connection path for remote Streamable HTTP MCP clients. Manual sfp_mcp_... bearer tokens remain an advanced fallback for clients that cannot complete OAuth.

Step-By-Step

1. Open /dashboard/settings/mcp.
2. Copy the Streamable HTTP endpoint.
3. Add the endpoint to an OAuth-capable MCP client.
4. Sign in and approve the account, project access, and scopes.
5. In the client, call shipfoundry.list_projects.
6. Call shipfoundry.get_setup_status for the project.
7. Call shipfoundry.list_relevant_updates.
8. Call shipfoundry.get_update_context for one update.
9. Call shipfoundry.get_task_packet for a compact task packet.
10. Confirm whether the packet is a Hand To Agent implementation or an investigation-first lane.
11. Verify the local repository directly.
12. Record the result with shipfoundry.record_update_outcome.

Available Agent Workflow Tools

The MCP server exposes the core update workflow:

• shipfoundry.list_projects
• shipfoundry.get_setup_status
• shipfoundry.update_project_context
• shipfoundry.list_relevant_updates
• shipfoundry.get_update_context
• shipfoundry.get_latest_handoff_brief
• shipfoundry.get_handoff_brief
• shipfoundry.get_task_packet
• shipfoundry.mark_brief_used
• shipfoundry.record_update_outcome

What ShipFoundry Does

• Keeps raw credentials out of chat prompts when OAuth is available.
• Validates audience, expiry, revocation, scopes, account membership, and project access.
• Lets an agent retrieve context without broad Linear sync.
• Lets the agent record outcomes after local inspection.
• Keeps Linear optional and GitHub read-only; project setup requires one selected repository.

What ShipFoundry Does Not Do

• It does not give the MCP client provider tokens for GitHub, Linear, OpenAI, Supabase, Stripe, or Resend.
• It does not replace local repo verification.
• It does not automatically implement recommendations.
• It does not require Linear before task packets are useful.
• It does not make manual bearer tokens the preferred path when OAuth works.

Troubleshooting

If the MCP client says auth is required, confirm it has completed OAuth or is sending the fallback bearer token.

If the client sees no projects, confirm the approved account and project scope.

If a task packet is unavailable, the update may be monitor-only, optional, or not ready for local-agent work.

If a fallback token is needed, store it in an environment variable instead of pasting it into chat.

Related Pages

• Brief format: Investigation Briefs
• End-to-end path: Agent Workflows
• Example artifact: Sample Engineering Spike
• Safety states: Trust And Readiness
• Linear export: Linear
• Product CTA: Start 7-Day Trial