MCP Gateway — How to Use

Developer

Prerequisites

Before connecting to the MCP Gateway, ensure you have:

1. Access to your Prodgy workspace
2. An API Token or an application that supports OAuth 2.1

There are two ways to connect:

Method	Best for	Token management
API Token	CLIs and local tools (Claude Code, Cursor, Windsurf)	Manual — you generate and paste the token
OAuth 2.1	Web applications and platforms	Automatic — the application handles everything

---

Method 1: API Token (manual setup)

Generate an API Token from Workspace Settings > API Tokens, then configure your tool.

Option A — Via CLI (recommended for Claude Code)

claude mcp add --transport http prodgy https://your-prodgy-url/mcp \
  --header "Authorization: Bearer prodgy_your_token_here"

This automatically writes the correct configuration to your .mcp.json file.

Option B — Manual configuration

Add the following to your AI tool’s MCP settings file:

{
  "mcpServers": {
    "prodgy": {
      "type": "http",
      "url": "https://your-prodgy-url/mcp",
      "headers": {
        "Authorization": "Bearer prodgy_your_token_here"
      }
    }
  }
}

Caution

The "type": "http" field is required when editing the config file manually. Without it, Claude Code does not know how to connect to the remote server. If you used the CLI (Option A), this field is added automatically.

Where to save

Tool	Configuration file
Claude Code	.mcp.json (project root) or ~/.claude/mcp.json (global)
Cursor	.cursor/mcp.json (project root)
Windsurf	~/.codeium/windsurf/mcp_config.json
Claude Desktop	Claude Desktop MCP settings

After saving, restart your AI tool. You should see Prodgy tools listed in the MCP tools panel.

Note

Use the same URL as your Prodgy workspace, with the /mcp path.

---

Method 2: OAuth 2.1 (for applications that support it)

If the application you are using supports OAuth 2.1 (for example, some web platforms, automation tools, or custom integrations), you can connect it to Prodgy without manually generating a token.

What you need to do:

1. In the third-party application, look for an option to add an MCP server or external connection
2. Enter your Prodgy MCP URL: https://your-prodgy-url/mcp
3. The application will start the OAuth flow automatically — you will be redirected to Prodgy
4. Log in (if not already), select the organization, product, and permissions you want to grant
5. Click Authorize — the application is now connected

That’s it. The application manages tokens automatically — no copy/paste, no expiration to worry about.

Note

Not all tools support OAuth yet. CLI tools like Claude Code, Cursor, and Windsurf currently use API Tokens (Method 1). Check your application’s documentation to see if it supports OAuth 2.1 for MCP connections.

After connecting, you can manage the application in Workspace Settings > Apps — view permissions, last usage, and revoke access if needed.

---

Verifying the Connection

Once configured, you can verify the connection by asking your AI tool to:

1. List tools — ask “What Prodgy tools are available?” and check that platform tools appear.
2. Get project context — ask “Get my Prodgy project context” to verify connectivity.
3. Search knowledge — ask “Search for [topic] in the knowledge base” to test RAG search.

Troubleshooting

Problem	Solution
No tools listed	Check that the URL in the config is correct
Cannot connect / no response	Add "type": "http" to your MCP config (required for remote servers)
“Unauthorized” error	Verify your API Token is valid and has the correct permissions
”Connection refused”	Check the Gateway URL with your administrator
”Forbidden” on restricted tools	Your API Token must belong to a user with the SUPERADMIN or ADMIN role

---

Using Prodgy Tools

Once connected, your AI coding assistant has access to all Prodgy tools. Here are some common use cases:

Get Product Context

Ask your AI tool: “Get the Prodgy project context” — returns product vision, OKRs, target audience, and active integrations.

Search Knowledge Base

Ask: “Search the knowledge base for authentication flow” — performs semantic (RAG) search across all indexed documents.

Manage Work Items

• “Create a PBI for user authentication improvements”
• “Search for open bugs assigned to me”
• “Update work item #123 status to Done”

Execute Agents

Ask: “List available Prodgy agents” then “Run the backlog prioritization agent” — triggers a Prodgy AI agent with its own tools and system prompt.

Install Integrations

Ask: “Show me the integration catalog” then “Install the Azure DevOps integration with my PAT token” — the AI will use install_integration to provision the integration with your credentials. No need to visit the Prodgy UI.

Manage Integration Templates (SUPERADMIN/ADMIN only)

Ask: “Create an integration template for Zendesk” — the AI will use the configured rules to generate a valid integration template, then offer to install it immediately.

---

Next Steps

• Overview — transport modes and available tools
• How It Works — tool discovery, execution flow, and access control