Connect your agent
to G2X.

Quickstart

1. Have a G2X account and review G2X plans. Choose a client that supports remote MCP over Streamable HTTP.
2. Add https://mcp.g2x.com/mcp as a remote MCP server.
3. Initialize the connection and discover schemas with tools/list.
4. Complete your client's registered OAuth setup, sign in with G2X, then ask something like “Find federal cybersecurity opportunities.” Your client calls the appropriate tool.

This example shows the endpoint only. You also need the OAuth client ID registered for your client; get the correct setup from G2X support. Installing the agent skill does not connect or authorize your account.

{
  "mcpServers": {
    "govcon": {
      "url": "https://mcp.g2x.com/mcp"
    }
  }
}

Add the GovCon MCP skill for guidance on choosing tools, keeping citations and completing account workflows.

Tool discovery is available for client setup; every data or tool call requires an authenticated G2X account. The transport is stateless, so do not depend on a server session ID.

Authentication

Use G2X OAuth in clients that support it. Unauthenticated tool calls return HTTP 401 with a WWW-Authenticate header that links the OAuth protected-resource metadata. Follow the advertised authorization server's authorization-code flow with PKCE S256.

Use the OAuth registration for the client you are connecting. Claude Code, hosted Claude, ChatGPT and Cursor have different callback requirements. Contact G2X support for the correct client ID and setup. A G2X API key is not a replacement for this sign-in flow. Keep credentials in the client's connection settings, never in a URL or a prompt.

Every tool requires authentication. Your account determines access and allowances. Signing in never grants access to another account's watchlist, workspace or analysis.

Tool catalog

MCP tools/list is the authoritative source for input schemas, descriptions and annotations. Read the schema before constructing arguments. Record IDs must come from search results.

Document formats and completeness

Ask for the complete document in Markdown, JSON or both. Markdown is for readable text; JSON preserves the supplied document structure. A page, excerpt or list of document names does not satisfy that request. Keep the document version, tables and citations with the result.

If your connection cannot return a complete artifact, use a supported source-document link. Do not present partial text as the full document or start analysis just to obtain it.

Capture workflow

1. Find an opportunity and keep its record ID.
2. Retrieve stored document content and existing analysis first. Keep each document's version and citations, and distinguish complete artifacts from excerpts.
3. Use the user's chosen agent for new interpretation, qualification and drafting by default. Save requested outputs through supported G2X actions. Do not start hosted analysis merely to read documents or save work.
4. Only if the user explicitly chooses G2X-hosted analysis, select the documents and use g2x_shred_opportunity for requirements or g2x_qualify_opportunity for company fit. Follow the connected tool schemas.
5. For a hosted run, poll g2x_get_analysis_run with the returned run ID. An accepted run is not a completed result. Retrieve the compliance matrix with the qualification run ID when its schema requires that identifier.

Make only the account changes the user asked for, and resolve an ambiguous target before acting. If a response is slow, resume the run by its existing ID instead of starting another.

Plans and usage

G2X pricing is the source for G2X plans and features. Sign in with your G2X account; its permissions apply to every tool. Your AI assistant or model subscription is separate.

The service applies usage and request limits. Each plan also sets a pace, a number of requests a minute, shared by all of your connections. Checking your usage or an analysis run's status does not count toward it. When a request goes past a limit, it returns HTTP 429 with a message that names the limit and when to try again, for example “You've reached your plan's limit of 30 requests a minute. Try again in 2 seconds.” Wait that long; repeating the request sooner will not increase your access.

Open your G2X account menu to check Lumen usage. An agent can report the balance only when its connection provides an account-usage capability. A request limit is not a price, and it is not a measure of your remaining Lumen usage. Do not estimate an account balance from the number of tool calls. Machine-readable access information.

When to add Tango

Use GovCon MCP to research markets, analyze opportunities and manage work in G2X. Add Tango by MakeGov when you need direct procurement data for your own software, data warehouse or custom analysis. Tango offers an API, SDKs and its own MCP connection.

G2X Professional members receive 50% off any Tango plan. Contact G2X support for help applying the member discount.

Errors & recovery

• 401: Reconnect using the authentication method configured in your client. For OAuth, check the client registration and callback with G2X support.
• 429: You reached a limit. The message says which one and when to try again; wait that long and do not retry in a loop.
• 503: G2X is busy right now. The request did not run; try again in a few seconds.
• Tool error: Inspect isError and the returned message. Check the input schema, your access and the required preceding workflow step.
• 405 on GET /mcp: Use MCP JSON-RPC POST requests with Content-Type: application/json and Accept: application/json, text/event-stream. The endpoint is not a browser page.

When no record matches, refine the question instead of inventing a result. Use bounded retries and keep run IDs for analysis requests.

Machine discovery

• Agent skill manifest: complete package and file checksums
• llms.txt: product and documentation index
• llms-full.txt: complete text guide
• MCP server manifest: remote transport
• MCP server card: domain discovery
• API catalog: interface documentation
• Sitemap: public pages

Request the home page or this guide with Accept: text/markdown for the text version. Responses include Vary: Accept.

Versioning: the MCP handshake negotiates the protocol version. Tool schemas are discoverable at connection time, so review them when you upgrade your client.