GOVCON MCP / DEVELOPER GUIDE
Build with
GovCon MCP.
The intelligence layer for GovCon growth. A developer guide to composing G2X research and account tools into a complete client workflow, from tool discovery to the result the member can use.
Build a workflow
Begin with the member's task, then inspect the tools offered by the authenticated connection. Use the tool reference to choose a discovery, detail, document or account-action step before constructing its arguments.
Carry returned identifiers between steps. A company search result, a public opportunity and a CRM account are different destinations; resolve the intended record before reading more detail or saving work.
Keep reading and analysis as separate choices. Retrieve existing documents and results first, then start G2X-hosted analysis only when the member requests it. Continue an accepted analysis with its returned run identifier.
Quickstart
You need a G2X account; review G2X plans.
- Add
https://mcp.g2x.com/mcpto your agent as a remote MCP server. Find your agent's steps. - Sign in with your G2X account when your agent asks.
- Ask “Look up [Company Name or UEI] in G2X.”
Installing the agent skill does not connect or authorize your account.
Add the GovCon MCP skill for guidance on choosing tools, keeping citations and completing account workflows.
Sign in before tool discovery: tools/list and every data or tool call require an authenticated G2X account. The transport is stateless, so do not depend on a server session ID.
Official integrations
G2X's own listings on other platforms.
G2X in ChatGPT
G2X's official plugin in ChatGPT, published in ChatGPT's plugin directory.
- Open G2X in ChatGPT's plugin directory.
- Choose Install plugin.
- Sign in with your G2X account when ChatGPT asks.
A G2X account is required. Every G2X plan works, including the free Community Edition.
G2X in ChatGPT's plugin directory
G2X GovCon Growth OS (Grok Bot)
G2X's own bot, published on xAI's Grok Bot.
- Open G2X GovCon Growth OS on x.ai.
- Choose Add to Grok Bot, then finish in the Grok Bot app.
- When Grok Bot prompts you to connect G2X, sign in with your G2X account to approve.
G2X on Vercel Connect
G2X's connector on Vercel Connect, for the apps and agents you deploy on Vercel.
- Open G2X on Vercel Connect and choose Create Connector, or run vercel connect create g2x in your linked project.
- In your app, request a G2X token for each signed-in user with the Vercel Connect SDK. The first time, send the user to sign in with their G2X account.
- Use the token with your MCP client at https://mcp.g2x.com/mcp.
Each user needs a G2X account. Every G2X plan works, and each user's plan sets what G2X returns.
Connect via MCP
Every agent that supports MCP connects to G2X: add https://mcp.g2x.com/mcp and sign in with your G2X account. Pick your agent for its steps.
Tested: a working G2X connection is on record. Steps checked: the steps follow the agent's own guide.
ChatGPT
Steps checked
ChatGPT is an AI agent. Install the G2X plugin from ChatGPT's plugin directory, or add G2X yourself as a custom MCP server.
The quickest way: G2X's official plugin, published in ChatGPT's plugin directory.
- Open G2X in ChatGPT's plugin directory.
- Choose Install plugin.
- Sign in with your G2X account when ChatGPT asks.
A G2X account is required. Every G2X plan works, including the free Community Edition. What ChatGPT can see and do follows your G2X account's permissions.
Or add G2X yourself as a custom MCP server:
- In ChatGPT on the web, go to chatgpt.com/plugins, choose +, then Add custom MCP server. If ChatGPT asks, turn on Developer mode first.
- Enter G2X as the name. Under Connection, enter https://mcp.g2x.com/mcp as the Server URL. For Authentication, choose the sign-in option.
- Read the warning, choose I understand and want to continue, then choose Create as a plugin.
- Open your personal plugins at chatgpt.com/plugins?view=personal, open G2X and choose + to install it. If you created it in a workspace, it's in that workspace's plugins.
- Sign in with your G2X account when ChatGPT asks.
In a Business, Enterprise or Edu workspace, your admin turns on plugins with MCP servers, and then Add custom MCP server appears.
Steps checked against G2X in ChatGPT's plugin directory and the ChatGPT guide to connecting a server.
Claude
Tested
Claude is Anthropic's AI agent. You add G2X once as a custom connector.
- In Claude, open Customize → Connectors.
- Choose + Add, then Add custom connector.
- Enter G2X as the name and https://mcp.g2x.com/mcp as the server URL, then choose Continue until Claude shows its sign-in settings.
- Keep Sign in now, choose Register automatically, then choose Add. If Claude shows Advanced settings instead, leave the client ID and client secret blank and choose Add.
- If Claude shows Connect, choose it. Sign in with your G2X account.
- Choose Allow to connect your account to Claude.
- In a new chat, choose +, then Connectors, and turn on G2X. Ask “Look up [Company Name or UEI] in G2X.” If Claude asks to use a G2X tool, review the request and choose Allow once.
On the Free plan you can add one custom connector. On a Team or Enterprise plan, an owner adds G2X once in Organization settings → Connectors (Add → Custom → Web), with the same name, address and sign-in settings. Everyone else then opens Customize → Connectors, finds G2X and chooses Connect.
Grok Bot
Steps checked
Grok Bot is an AI agent on the web and on iOS and Android. You add G2X once as a custom connector.
- Go to grok.com/connectors. In the mobile app, open Settings → Connectors.
- Choose New Connector, then Custom.
- Paste https://mcp.g2x.com/mcp and sign in with your G2X account.
On a business or enterprise account, an admin sets up the connector for your team first.
Steps checked against the Grok Bot connectors guide.
Microsoft Copilot
Steps checked
Microsoft Copilot uses G2X through Microsoft 365, with a work or school account. A Copilot Studio maker adds G2X to an agent, and people in your organization use that agent in Microsoft Copilot.
Add G2X to a Copilot Studio agent
- In Copilot Studio, open your agent and go to Tools. Choose Add a tool → New tool → Model Context Protocol.
- Enter G2X as the server name, a short description, and https://mcp.g2x.com/mcp as the server URL.
- For authentication, choose the sign-in option, then Dynamic discovery. Choose Create.
- Choose Create a new connection, sign in with your G2X account, then choose Add to agent.
- Publish the agent to the Teams and Microsoft 365 channel, so people can use it in Microsoft Copilot.
Microsoft 365 admins can also add MCP servers for the whole organization as connectors in the Microsoft 365 admin center. The Copilot app for a personal Microsoft account connects only to a fixed list of services, such as OneDrive and Gmail. It can't add G2X.
Steps checked against Microsoft's guide to adding an MCP server to an agent and Microsoft's guide to connecting Copilot to other services.
Gemini
Steps checked
Gemini is Google's AI agent. Add G2X to the Gemini app on the web, or to Gemini CLI in your terminal.
Gemini app
- On gemini.google.com, open Settings, then Connected Apps.
- Under Custom apps, choose Add a custom app and paste https://mcp.g2x.com/mcp.
- Choose Next, then sign in with your G2X account.
Google offers custom apps to personal Google Accounts of people 18 or older in the US, using Gemini in English with Keep Activity on.
Gemini CLI
gemini mcp add --transport http govcon https://mcp.g2x.com/mcp- Gemini CLI finds the G2X sign-in on its own. Sign in with your G2X account when it asks.
Steps checked against Google's help on custom apps in Gemini and the Gemini CLI guide to MCP servers.
Notion
Steps checked
Notion's AI agents can use G2X on Notion's Business and Enterprise plans. Add G2X to your Notion Agent, or to a Custom Agent your team shares.
Notion Agent
- In Notion, open Settings → Connections and choose the Discover tab.
- Choose Add Custom MCP and paste https://mcp.g2x.com/mcp.
- Sign in with your G2X account when Notion asks.
Custom Agents
- Open the agent's Settings and go to Tools & Access.
- Choose Add connection → Custom MCP server.
- Paste https://mcp.g2x.com/mcp as the server URL, enter G2X as the display name, then choose Connect.
- Sign in with your G2X account when Notion asks.
A workspace admin turns on custom MCP servers first, under Settings → Connections → Manage.
Steps checked against Notion's guide to MCP servers for your Notion Agent and Notion's guide to MCP connections for Custom Agents.
Muse
Steps checked
Muse Code is Meta's AI coding agent. You add G2X to its settings file, then sign in.
Muse Code
Add G2X to the mcp_servers block of ~/.config/muse/settings.json:
{
"mcp_servers": {
"govcon": {
"transport": "streamable_http",
"url": "https://mcp.g2x.com/mcp",
"enabled": true
}
}
}- Run muse mcp login govcon and sign in with your G2X account in your browser.
The G2X connector for the Muse app is anticipated to be live soon.
Steps checked against Muse Code's guide to MCP servers.
Cursor
Steps checked
Cursor is an AI code editor. You can add G2X in one click.
- Choose Add G2X to Cursor. Cursor opens to add the G2X server, named govcon.
- When Cursor opens your browser, sign in with your G2X account.
Add it by hand
Add G2X to ~/.cursor/mcp.json for all your projects, or to .cursor/mcp.json in one project:
{
"mcpServers": {
"govcon": {
"url": "https://mcp.g2x.com/mcp"
}
}
}Steps checked against Cursor's guide to MCP install links and Cursor's MCP guide.
Zapier
Steps checked
Zapier connects your apps in automated workflows called Zaps. Its MCP Client app, in beta, connects G2X.
- In Zapier, open Apps, choose Add connection, and search for MCP Client.
- Paste https://mcp.g2x.com/mcp as the server URL and choose Streamable HTTP.
- For the sign-in setting, choose Yes.
- Choose Continue and sign in with your G2X account.
- Use MCP Client actions in your Zaps to call G2X.
Steps checked against Zapier's MCP Client guide.
Devin
Steps checked
Devin is an AI software engineer. An organization admin adds G2X once for the team.
Devin
- Open Customize → MCPs and choose Add custom MCP.
- Enter G2X as the name, choose HTTP as the transport, and paste https://mcp.g2x.com/mcp.
- For authentication, choose the sign-in option, for the whole organization or for each person. Then sign in with your G2X account.
Devin CLI
devin mcp add govcon https://mcp.g2x.com/mcp
devin mcp login govcon- Sign in with your G2X account when Devin CLI asks.
Devin Desktop
Devin Desktop, formerly Windsurf, reads its servers from an MCP config file.
- In the Cascade panel, open the … menu and choose Open MCP config file.
- Add a server named govcon with serverUrl set to https://mcp.g2x.com/mcp, then save the file.
- Sign in with your G2X account when Devin Desktop asks.
Steps checked against Devin's MCP guide, the Devin CLI MCP guide and the Devin Desktop MCP guide.
Claude Code
Steps checked
Claude Code is Anthropic's AI coding agent for your terminal. You add G2X with one command.
claude mcp add --transport http govcon https://mcp.g2x.com/mcp- In Claude Code, type /mcp, choose govcon and sign in with your G2X account in your browser.
Steps checked against the Claude Code guide to MCP.
VS Code
Steps checked
VS Code is Microsoft's code editor. Its chat, including GitHub Copilot, can use G2X once you add the G2X server. You can add it in one click.
- Choose Install G2X in VS Code. Or run MCP: Add Server from the Command Palette, choose HTTP, paste https://mcp.g2x.com/mcp and name it govcon.
- When VS Code opens your browser, sign in with your G2X account.
If your organization uses GitHub Copilot Business or Enterprise, an admin turns on the MCP servers in Copilot policy first.
Steps checked against VS Code's MCP guide and GitHub's guide to MCP in Copilot Chat.
OpenAI Codex
Steps checked
Codex is an AI coding agent. The Codex CLI, the Codex IDE extension and the ChatGPT desktop app share one setup, so you add G2X once.
Codex CLI
codex mcp add govcon --url https://mcp.g2x.com/mcp
codex mcp login govcon- codex mcp login govcon opens your browser. Sign in with your G2X account.
Codex in the app or your editor
- In the ChatGPT desktop app or the Codex IDE extension, open Settings → MCP servers → Add server.
- Choose Streamable HTTP and paste https://mcp.g2x.com/mcp.
- Choose Authenticate and sign in with your G2X account, then restart the app.
Steps checked against the Codex guide to MCP.
Perplexity
Steps checked
Perplexity is an AI answer engine. You add G2X once as a custom remote connector.
- Open Account settings → Connectors and choose + Custom connector.
- Choose Remote.
- Enter G2X as the name and https://mcp.g2x.com/mcp as the MCP server URL.
- For Authentication, choose the sign-in option. For Transport, choose Streamable HTTP.
- Check the acknowledgement box and choose Add.
- Choose the G2X card to sign in with your G2X account and turn the connector on.
On Perplexity Enterprise, members add custom connectors after an admin allows it.
Steps checked against Perplexity's guide to custom remote connectors.
Le Chat
Steps checked
Le Chat is Mistral AI's agent. An admin adds custom connectors. On Free, Pro and Student plans, the account owner is the admin.
- Open the Connectors page and choose + Add Connector.
- Choose the Custom MCP Connector tab.
- Enter g2x as the name, with no spaces, and paste https://mcp.g2x.com/mcp.
- Choose Connect. Le Chat finds the G2X sign-in on its own.
Steps checked against Mistral's guide to MCP connectors in Le Chat.
Manus
Steps checked
Manus is an AI agent that works through tasks for you. You add G2X once as a custom MCP server.
- Open Settings → Integrations → Custom MCP Servers and choose Add Server.
- Enter G2X as the name, paste https://mcp.g2x.com/mcp, and add the server.
Steps checked against Manus's guide to custom MCP servers.
Factory
Steps checked
Droid is Factory's AI coding agent. You add G2X to it from your terminal.
droid mcp add govcon https://mcp.g2x.com/mcp --type http- In Droid, type /mcp and choose govcon.
- Sign in with your G2X account when your browser opens.
Steps checked against Factory's MCP guide.
n8n
Steps checked
n8n is a workflow automation tool. Its MCP Client nodes connect G2X to a workflow or to an AI Agent.
- Add an MCP Client node to your workflow, or an MCP Client Tool node to an AI Agent.
- Choose the streamable HTTP transport and paste https://mcp.g2x.com/mcp as the MCP endpoint URL.
- For Authentication, create an MCP sign-in credential with Dynamic Client Registration turned on.
- Sign in with your G2X account.
Steps checked against n8n's MCP Client node guide and n8n's MCP credentials guide.
Make
Steps checked
Make is a visual automation platform. Its MCP Client module connects G2X to a scenario.
- Add the MCP Client module to a scenario and choose Create a connection.
- Choose + New MCP Server and paste https://mcp.g2x.com/mcp.
- If Make asks how to sign in, choose the sign-in option. Save the connection.
- Sign in with your G2X account.
Steps checked against Make's MCP Client guide.
Replit
Steps checked
Replit Agent builds apps for you. You add G2X once as an MCP server.
- Choose Add G2X to Replit, finish the install in Replit, and sign in with your G2X account when Replit asks.
- Or go to replit.com/integrations, scroll to MCP Servers for Replit Agent and choose + Add MCP server. Enter G2X as the name, paste https://mcp.g2x.com/mcp, then choose Test & save and sign in with your G2X account.
Steps checked against Replit's guide to connecting via MCP and Replit's guide to MCP install links.
Hermes Agent
Steps checked
Hermes Agent is an open-source AI agent from Nous Research.
Option A: commands
Run these in your terminal:
hermes config set mcp_servers.govcon.url https://mcp.g2x.com/mcp
hermes config set mcp_servers.govcon.auth oauth
hermes config set mcp_servers.govcon.oauth.cimd false
hermes mcp login govconThe last command opens your browser so you can sign in.
Option B: edit config.yaml
Open ~/.hermes/config.yaml and add G2X under mcp_servers:
mcp_servers:
govcon:
url: "https://mcp.g2x.com/mcp"
auth: oauth
oauth:
cimd: false- Save the file. Then, in a new terminal window, run hermes mcp login govcon.
Steps checked against Hermes Agent's MCP guide and MCP config reference.
Any agent via MCP
Other agents need to support remote MCP servers with sign-in. Add https://mcp.g2x.com/mcp as a remote MCP server, then sign in with your G2X account when your agent asks.
Authentication
Use G2X OAuth in clients that support it. Without G2X sign-in, tools/list and every tool call 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.
Claude connects with the server URL alone. Every agent under Connect via MCP follows its own steps to the same sign-in. 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.
Every tool, with inputs and examples
g2x_calibrate_session
Start a company-aware research workflow here. Establish which company the member is working for before searching for a fit; keep that company context distinct from the companies returned as competitors or potential partners.
g2x_search_opportunities
Use opportunity search to build a shortlist before requesting notice details. Keep the returned record identifiers with each result so a later g2x_get_record call opens the selected notice rather than repeating a title search.
g2x_search_records
Use record search when the workflow needs individual matching records. Preserve the search scope and record links in the result; use g2x_query for supported counts or aggregates rather than estimating a market total from a page of matches.
g2x_search_supplementary
Use this discovery path for the supplementary solicitations described in the tool contract. Keep a match in document text separate from a confirmed requirement; open the relevant document before making a qualification claim.
g2x_opportunity_attachment_text
Use this reading step before interpreting a solicitation. Follow the returned document format and continuation information until the requested material is complete; label an excerpt as an excerpt rather than presenting it as the whole file.
g2x_get_record
Add a detail step after the user selects an opportunity or company. Carry the identifier from the search result into this call and preserve the returned record link beside any summary your application produces.
g2x_forecast_scan
Build an advance-planning view around agency forecasts. Present a forecast as an expected acquisition, with its stated timing, rather than treating it as an open solicitation with a bid deadline.
g2x_recompete_radar
Use this in a workflow that connects expiring work to possible follow-on opportunities. Keep an existing award and a possible recompete as separate records so your application does not imply that the agency has announced a replacement.
g2x_expiring_awards
Use award end dates to assemble an account-planning shortlist. Keep the period of performance visible when explaining why a contract appeared; an approaching end date alone does not establish a recompete or an open notice.
g2x_search_companies
Resolve a company before enriching it or saving CRM work. Show the returned identifiers and distinguishing facts when names are similar; do not attach one company's awards or contacts to a different company with a similar name.
g2x_company_contract_history
Add contract history to an incumbent or partner research flow. Retain award identifiers, dates and the stated scope of the answer so your agent can explain which past-performance records support its assessment.
g2x_teaming_partners
Build a candidate partner list around the user's capabilities and market criteria. Keep the evidence behind each candidate and review the company identity before turning a research result into a CRM account or an outreach task.
g2x_vehicle_usage
Add vehicle usage to a contract-vehicle research workflow. Keep the vehicle identity and the scope of the returned work with the analysis before comparing holders or discussing an addressable market.
g2x_socioeconomic_status
Use this to investigate a resolved company's socioeconomic status. Preserve the returned evidence and its scope; do not convert an absent result into a claim that the company lacks a certification.
g2x_search_events
Start event discovery with the member's subject, location and time window. Keep the selected event's identifier for g2x_get_event so a meeting-preparation workflow can retrieve the event details before offering next steps.
g2x_get_event
Retrieve the selected event after discovery, then carry its date and registration information into the meeting brief. Reading an event does not register the member or add it to a calendar.
g2x_watch_records
Offer watchlist saving after the member selects research results. Use the selected record identifiers and inspect both additions and skipped items in the response before saying that every requested record is being watched.
g2x_company_signals
Add company announcements to an account-research brief. Keep the announcement source and date with the summary, and separate what the company announced from your agent's interpretation of what it might mean for a pursuit.
g2x_company_web_profile
Use the public company page as a source in company research. Keep the page identity and cited posts with the answer; do not merge a public web profile into a claimed G2X company profile without the requested account action.
g2x_opportunity_documents
Begin solicitation review by identifying the available documents and amendments. Use the returned document identities to choose what to read, and preserve versions so later analysis can distinguish the controlling material from an older file.
g2x_prepare_opportunity_documents
Use document preparation when the member has chosen a G2X analysis workflow that needs it. Keep preparation separate from simply reading existing documents, and review the returned document list. To discover existing analysis for this opportunity, call g2x_get_analysis_run with opportunity_id.
g2x_shred_opportunity
Use requirements extraction only when the member chooses G2X-hosted analysis. Keep the selected solicitation versions with the run, then inspect the returned analysis result before using extracted requirements in a compliance review.
g2x_qualify_opportunity
Connect a selected opportunity and the intended company profile for a requested G2X Bid/No-Bid assessment. Keep the returned run identifier and retrieve its outcome; starting an assessment does not establish that the company qualifies.
g2x_compliance_matrix
Retrieve the matrix for the analysis run the member is reviewing. Keep requirement citations and unresolved gaps available with the matrix; a generated row is a review aid, not proof that a proposal meets the requirement.
g2x_get_analysis_run
Use the existing run identifier to resume an analysis journey. Keep an accepted or unfinished run distinct from a delivered result, and avoid starting the same analysis again merely because the client needs another status check.
g2x_nsn_lookup
Use an exact National Stock Number to open an item-focused research path. Keep that item identifier with supplier context and follow its source records before inferring that a supplier can meet a particular solicitation.
g2x_nsn_search
Start here when the user has an item description or supply class instead of an exact National Stock Number. Let the user select the intended item, then carry its identifier into the detailed lookup.
g2x_crm_find
Begin a CRM workflow by resolving records the member can access. Keep CRM identifiers distinct from public company or opportunity identifiers so a later note, task or contact update targets the intended account record.
g2x_crm_get_record
Read the selected CRM record before preparing an account update or meeting brief. Preserve its CRM identity through the workflow and distinguish existing account facts from new information the user wants to add.
g2x_crm_save_account
Use this after the member asks to keep a company as a CRM account. Resolve the company and inspect existing CRM matches first, then retain the saved destination so your interface can link the member to the resulting account.
g2x_crm_save_contact
Use contact saving after resolving the person and intended CRM account. Review the member's requested contact details before the call and retain the returned destination rather than claiming that a research result was already saved.
g2x_crm_add_note
Attach a requested note to the resolved CRM record. Keep the member's text and target together through confirmation, then read the tool's outcome before reporting that the account history has changed.
g2x_crm_log_interaction
Use this to record an interaction the member wants in CRM history. Keep who participated, what happened and the intended record together; a meeting-preparation brief alone is not an instruction to log an interaction.
g2x_crm_set_follow_up
Turn an agreed next step into a follow-up on the selected CRM record. Resolve any ambiguous target or date before sending the account change, and use the returned outcome when telling the member what was recorded.
g2x_crm_add_task
Create a task only after the member has chosen the work and its CRM destination. Carry the requested due date and task text with that record, then show the resulting task outcome in the pursuit workflow.
g2x_unwatch_records
Resolve the watched records before removing them. Present the member's selected removals clearly and inspect the outcome for each record; a closed opportunity in a search result is not itself a request to unwatch it.
g2x_list_watchlist
Use the member's watchlist as the starting point for a saved-interest review. Preserve watched record identities when offering to open a record, add it to a pursuit or remove a watch.
g2x_save_search
Save a research scope when the member asks to reuse it. Keep the chosen name and filters together, then retain the saved search identity for later runs or updates rather than reconstructing it from the name alone.
g2x_list_saved_searches
Let the member choose an existing search before running or editing it. Keep the returned search identity with its name and scope so similarly named views remain separate choices.
g2x_update_saved_search
Read and resolve the saved search before changing its filters. Keep the requested edit separate from the rest of the existing search, then inspect the returned result before describing the revised research scope.
g2x_run_saved_search
Use the selected saved search to repeat its research scope. Keep the search identity with the returned results, and distinguish running the search from changing its name or filters.
g2x_list_pipelines
Use the accessible pipeline list to choose a destination for pursuit work. Keep the selected pipeline identity rather than assuming that a familiar name identifies the same pipeline for every member.
g2x_get_pipeline
Read the selected pipeline before offering stage changes or pursuit updates. Preserve the pipeline and item identities with their displayed stages so the next action targets the specific pursuit the member selected.
g2x_add_to_pipeline
Add a selected opportunity only after the member chooses its pipeline destination and stage. Carry the opportunity identity from research and inspect the returned pursuit before claiming it has been added.
g2x_move_pipeline_item
Use an existing pursuit item and the member's selected destination stage. Resolve both in the intended pipeline before sending the move; a recommendation to advance a pursuit is not the completed stage change.
g2x_add_pipeline_note
Keep a requested pursuit note attached to the selected pipeline item. Preserve the distinction between the member's account note and cited research evidence, then inspect the save outcome before reporting completion.
g2x_list_pipeline_notes
Read pursuit notes when preparing an account review or continuing capture work. Keep each note associated with its pursuit so a summary cannot accidentally attribute another opportunity's discussion to this one.
g2x_remove_from_pipeline
Use this when the member asks to remove a specific pursuit from a pipeline. Confirm the intended item before the call and distinguish this removal from deleting the underlying public opportunity record.
g2x_create_pipeline
Create a new pursuit workspace when the member requests one. Check accessible pipelines first when a name could refer to an existing destination, then retain the created pipeline identity for subsequent additions.
g2x_delete_pipeline
Treat deletion as a separate, explicit account action. Resolve the exact pipeline and review the user's request before calling this tool; do not substitute deletion for removing one pursuit item.
g2x_list_ai_profiles
Let the member select the company context intended for G2X analysis. Keep profile identity and readiness information with the choice before starting a Bid/No-Bid assessment for an opportunity.
g2x_get_ai_profile
Read the selected AI profile before using it in an assessment or preparing an update. Keep its company context visible so a business-line profile is not silently substituted for a different profile.
g2x_create_ai_profile
Use profile creation for a company or business line the member wants to assess separately. Review the requested profile content before saving it and retain the created profile identity for the later qualification workflow.
g2x_update_ai_profile
Resolve and read the intended AI profile before applying the member's requested change. Keep new certification or capability statements distinct from existing profile content and verify the save outcome before using the revised profile.
g2x_list_my_company_profiles
Use the member's claimed company profiles to resolve which company they can manage. Keep that account relationship separate from a public company search result before offering an update to the company's profile.
g2x_update_my_company_profile
Apply an explicitly requested company-profile change to the intended claimed company. Review the selected company and edited content before the call, then inspect the returned outcome before saying the public profile changed.
g2x_usage
Use the account's reported usage when the member asks about remaining capacity. Keep the returned periods and reset information with the answer; do not infer a usage balance from your client's count of tool calls.
g2x_search_government_people
Find government buyers by their notice-listed role, office or buying history. Preserve the returned person ID for a detail read.
g2x_get_government_person
Read the selected buyer's buying patterns and office history. Cite the linked notices for contact details and preserve both G2X and SAM.gov links where returned; reading does not contact the person.
g2x_query
Build a market question around an explicit dataset, time period and grouping. Keep the answer's coverage notes and distinguish the exact aggregate from any displayed sample; retain a returned or explicitly saved workbook when the user needs the larger answer.
g2x_save_query_workbook
Runs a list or search command and saves all fetched records as a workbook in your G2X account. This explicit action creates a new file. Use the separate read-only query to read without saving.
g2x_resolve
Use this when you have a PIID, award key, SAM UEI, solicitation number, notice id or company name and need the canonical id and the record_id the record read takes. Hyphens and spaces in a PIID are accepted. Do not use for keyword, agency or NAICS searches: use the procurement records search. Examples: {"query":"M67854-22-D-8001"}; {"query":"Meridian","kind":"company"}.
g2x_get_award
Use this when you need one federal award's facts by PIID or award key: holder (name, UEI, parent), awarding and funding agency, obligated, current value, ceiling (base and all options), current and potential end dates and an IDV's ordering end, each with its source. Do not use for finding awards (use the procurement records search) or an IDV's orders (use the IDV summary). Examples: {"identifier":"ZZ0001-26-D-0042"}, {"identifier":"CONT_AWD_ZZ000125C0107_9700_-NONE-_-NONE-"}.
g2x_idv_summary
Use this when you need one IDV's size and use in a single call: its ceiling (base and all options), its order count, the total obligated across its orders, and up to five largest orders by obligation among the first ten orders read (PIID, holder, obligated, end date). Do not use for a vehicle program spanning many IDVs (use the contract vehicle analysis) or one award's own facts (use the award facts read). Examples: {"idv":"ZZ0001-26-D-0042"}, {"idv":"CONT_IDV_ZZ000126D0042_9700"}.
g2x_award_transactions
Use this when a question needs one award's modification history: which modifications it has, what each one obligated (the change on that action, not a running total), which one last added funds, and the award's cumulative obligated total. Newest first, with dates, modification numbers and when served an action type and description. Do not use for finding awards by contractor, agency or keyword, or for comparing several awards. Examples: {"piid":"W912DY24C0012"}; {"piid":"W912DY-24-C-0012","positive_funding_only":true}.
spending
Keep the explicit award scope and period basis with every total. Supporting IDs are examples behind each top group; the total covers all matching groups, including those outside the displayed ranking.
recipient_profile
Keep direct recipient obligations separate from the parent family's obligations. An unavailable family total does not mean zero and must never be filled with the direct recipient amount.
g2x_search_tools
Use this when you do not know which G2X tool answers a question. Searches tool descriptions, field definitions and worked examples. Returns five distinct tools by default, with input schemas, matching fields, a recipe, required inputs and availability. Check needs before calling a tool; a relevant award or company reader may require an identifier or parent lookup first.
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
- Find an opportunity and keep its record ID.
- Retrieve stored document content and existing analysis first. Keep each document's version and citations, and distinguish complete artifacts from excerpts.
- 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.
- Only if the user explicitly chooses G2X-hosted analysis, select the documents and use
g2x_shred_opportunityfor requirements org2x_qualify_opportunityfor company fit. Follow the connected tool schemas. - For a hosted run, poll
g2x_get_analysis_runwith 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 agent 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.
Errors & recovery
- 401: Reconnect using the authentication method configured in your client. If sign-in keeps failing, contact 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
isErrorand 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/jsonandAccept: 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 once you are signed in, so review them when you upgrade your client.