Get2Post MCP Connector
Get2Post is a collaborative application programming interface (API) testing product. The Get2Post Model Context Protocol (MCP) connector lets an AI assistant browse a user's workspaces, requests, environments, and activity, and act on pending approval requests — all under that user's own Get2Post account and role. The assistant never gets broader access than the signed-in user already has.
Connecting from Claude
- Add Get2Post from the Claude connectors directory, or add it as a custom connector with server URL https://get2post.com/mcp.
- For Team or Enterprise Claude workspaces, an owner adds the connector from Organization settings > Connectors before members can connect it.
- Complete the OAuth (Open Authorization) sign-in with a Get2Post account.
- Review the requested scopes shown at consent and grant them to finish connecting.
Connecting from ChatGPT
- In ChatGPT, open Settings > Apps & Connectors and create a connector with server URL https://get2post.com/mcp.
- Complete the OAuth sign-in with a Get2Post account.
- Review the requested scopes shown at consent and grant them to finish connecting.
- Enable the connector in the conversation, then verify tool discovery before relying on it.
Prerequisites
- A Get2Post account. Sign-up may be invitation-only before general launch; an existing member or workspace owner can invite you.
- MCP (Model Context Protocol) access requires a paid plan — Pro, Team, Enterprise, or Enterprise+. It is not included on the Free plan.
- The connector can only reach what your account can already reach: workspace membership and your role's permissions still apply to every tool call.
Tool reference
These are the public tools the Get2Post MCP server exposes. Read tools only retrieve data; write tools change the state of an approval request.
| Tool | Description | Access |
|---|---|---|
describe_capabilities |
Describe the G2P MCP server's major capabilities, restrictions, and auth model so an AI agent can decide what to do next. | Read |
list_accessible_workspaces |
List the workspaces the current MCP actor can actually read in G2P. | Read |
get_workspace_snapshot |
Read a sanitized snapshot of a workspace, including workspace summary, folder tree, request summaries, and environment summaries. | Read |
get_environment_matrix |
Read the environment matrix for a workspace. Secret variable values are intentionally redacted from the MCP result. | Read |
get_activity_timeline |
Read the current activity timeline for a workspace, including audit and execution entries visible to the current MCP actor. | Read |
approve_approval_request |
Approve a pending approval request when the current MCP actor has approval authority in that workspace. | Write |
deny_approval_request |
Deny a pending approval request when the current MCP actor has approval authority in that workspace. | Write |
Security and data handling
- Authentication and authorization: OAuth 2.0 with PKCE (Proof Key for Code Exchange). No client secret is used or requested.
- Consent: the scopes a connector is requesting (
mcp.read,mcp.write,mcp.execute,offline_access) are shown at sign-in, and only the granted scopes are authorized. - Isolation: every delegated token is scoped to one workspace under one organization (tenant); a connector cannot read or write another organization's data.
- Revocation: sign in to Get2Post, open Settings, and revoke a delegated MCP grant at any time — this immediately invalidates that connector's access.
- Read the Terms of Service and Privacy Policy for the full commitments governing this data.
Support
Questions about the connector, or a problem connecting it, go to the same support channel as the rest of Get2Post.
Glossary
- AI
- Artificial intelligence.
- API
- Application programming interface.
- MCP
- Model Context Protocol.
- OAuth
- Open Authorization.
- PKCE
- Proof Key for Code Exchange.