MCP Gateway — Overview

Developer

What is the MCP Gateway?

The MCP Gateway is a Prodgy component that exposes your organization’s integrations, knowledge base, and AI agents as MCP tools — the standard protocol used by modern AI coding assistants.

This means tools like Claude Code, Cursor, Windsurf, and Claude Desktop can directly interact with your Prodgy workspace: creating work items, querying your knowledge base, executing agents, and managing integrations — all from within the developer’s IDE.

Tip

All tool execution happens server-side — credentials and secrets never leave the server.

---

Available Tools

Platform Tools

These tools are always available:

Tool	Description
get_my_profile	Returns the authenticated user identity, organization metadata and personal AI preferences. Auto-injected on session start.
get_workspace_info	Returns workspace context — vision, target audience, OKRs, active integrations. Auto-injected on session start.
update_my_ai_preferences	Updates the user’s personal AI directive (markdown) and the destructive-action confirmation flag
search_knowledge	Semantic search (RAG) on the workspace’s knowledge base
list_agents	List AI agents configured for the workspace
invoke_agent	Execute a Prodgy agent (with its own LLM, tools, and system prompt)
list_integration_catalog	List available integration templates
get_integration	Get details of an integration template
list_installed_integrations	List integrations currently installed in the organization
install_integration	Install an integration into the organization with credentials
create_integration	Create an integration template (SUPERADMIN/ADMIN role)
update_integration	Update an integration template (SUPERADMIN/ADMIN role)
delete_integration	Delete an integration template (SUPERADMIN/ADMIN role)
get_active_integrations	List active integrations for the organization
get_mcp_settings	Get MCP Server configuration (SUPERADMIN/ADMIN role)
update_mcp_settings	Update MCP Server instructions and rules (SUPERADMIN/ADMIN role)

Caution

Tools marked with SUPERADMIN/ADMIN role require the API Token to be associated with a user who has the SUPERADMIN or ADMIN role. Regular users will receive a “Forbidden” error.

Integration Tools

Beyond the platform tools, the MCP Gateway dynamically exposes tools from your organization’s active integrations. Each integration you configure in Prodgy (Azure DevOps, Jira, Slack, GitHub, etc.) automatically adds its own tools to the Gateway — no code changes needed.

This means the set of available tools grows as you add integrations, and your AI assistant can interact with all of them through a single MCP connection.

---

Dynamic Instructions

The MCP Gateway supports customizable instructions that define how AI clients should behave when interacting with your workspace. You can manage these instructions through:

1. Prodgy UI: Settings > MCP Server
2. MCP tool: call update_mcp_settings (requires SUPERADMIN role)

The instructions allow you to define behaviors such as always loading the project context first, how to handle integration errors, and rules for creating new integration templates.

---

Credential Security

The MCP Gateway supports multiple credential patterns for integrations, all resolved server-side:

• Header-based — e.g., Bearer {token}
• Query parameter — credentials injected into endpoint URLs
• Request body — credentials injected into request bodies
• OAuth2 client_credentials — automatic token exchange before each request
• Multi-step session — login + session token acquisition before each request

Note

Credentials are stored encrypted and resolved at execution time. The MCP Gateway never sees or transmits raw credentials.

---

Next Steps

• How It Works — tool discovery, execution flow, and access control
• How to Use — step-by-step setup for Claude Code, Cursor, Windsurf, and Claude Desktop