- Community
- Starter
- Pro
- Enterprise
Use the GovCon MCP skill and move your workflow to G2X
Install the complete skill and map your existing research and pursuit workflows to supported G2X actions.
On this page
Start with your existing work
The GovCon MCP skill gives your AI assistant written playbooks for working with G2X: choosing an available tool for the question, reading a solicitation completely, checking an incumbent without confusing a corporate family for one awardee, and saving a requested result where your connection supports it. The skill adds instructions; your MCP connection supplies the tools, and your G2X account permissions still apply.
Start with how you work today. The assistant should use the context you have already shared about your company, tools, and task, then ask only for a missing detail that changes the result. It should reason with its own model and reuse available G2X analysis. Choose new G2X analysis explicitly when you want it, rather than treating it as a routine step in research or saving.
Try: “I track VA opportunities in a spreadsheet and research incumbents in another service. Help me qualify this week's shortlist in G2X. Start with the spreadsheet I attached; do not change account records yet.”
The skill adds guidance. You still need a connected G2X account, and your seat's access still applies.
Install the whole skill
Find GovCon MCP in the skills.sh directory. Install from the public GovCon skills repository in your terminal:
npx skills add G2X-Team/govcon-skills --skill govcon-mcpChoose your assistant when prompted. For installation options and prerequisites, follow the repository's instructions and the skills CLI documentation.
This command runs the skills CLI through npx to add the skill's instructions and playbooks. Connect G2X separately through your assistant's normal remote MCP settings at https://mcp.g2x.com/mcp, following the client connection guide. Installing a skill does not sign you in or confirm that a G2X tool call works.
For a client that supports archive uploads, download the GovCon MCP skill archive from the official skill page. Keep the govcon-mcp directory together: SKILL.md is the entry point, and references contains the nested playbooks. Copying only SKILL.md leaves its links incomplete.
In a client that supports skill uploads, upload the complete archive using its skill installation controls. For a local assistant with a documented skills directory, extract the whole govcon-mcp folder there. Follow your client's installation instructions; adding an MCP server alone does not install a skill.
If your client does not load skills, provide the relevant playbook as task guidance where it supports attached instructions. Do not assume it can follow local file links it cannot access.
Let the task choose the playbook
The repository installation includes eleven playbooks. Your assistant should open only those needed for the job. If you install an archive, use the playbooks included with that package.
| Task | Nested playbook |
|---|---|
| Find opportunities, forecasts, or recompetes | references/opportunities.md |
| Size a market or research a vehicle | references/markets.md |
| Research a company, incumbent, partner, or person | references/companies.md |
| Prepare for events and meetings using available context | references/events.md |
| Read a solicitation or compare amendments | references/documents.md |
| Assess fit or review requirements | references/capture.md |
| Draft a brief, matrix, proposal, or response and save where supported | references/work-products.md |
| Organize a pursuit | references/pursuits.md |
| Work with G2X CRM records | references/crm.md |
| Move an existing workflow to G2X | references/migration.md |
| Connect your account or recover access | references/connection.md |
A playbook's topic does not guarantee that your connection offers every action it describes. Before drafting something you want saved, have the assistant check whether it can save to the intended G2X destination. It must inspect available tools and inputs, complete supported work, and give you the G2X app step for anything unavailable through MCP. If saving is unavailable, keep the draft in your assistant and state what remains to be added to G2X.
Map the workflow before moving records
Provide an example you are allowed to use: a current search, shortlist, pursuit, or export. The assistant should identify the outcome, map fields and decisions to G2X, and show what can transfer.
| What you use today | A G2X starting point |
|---|---|
| Repeated opportunity searches | Search filters and saved searches in the app |
| Companies or contracts to follow | Watchlists in the app |
| A spreadsheet of pursuits and next actions | Pipelines in the app |
| Account and contact notes | G2X CRM, using actions your connection offers |
| Solicitation files and qualification notes | Document research and capture workflows |
Compare a small sample first. Preserve identifiers, company identity, source links, dates, and ownership. Match stage names and field meanings before import; similar labels can represent different decisions. A file attached in chat has not been imported into G2X.
When you ask for a supported account change, the assistant should make it, read the record back, and report the result. Research alone does not authorize moving records, adding contacts, or sending outreach. Use the app for missing actions; do not invent a tool or silently drop a field.
Check the result
Ask for the completed research, G2X links, account changes actually made, and remaining app steps. Check records against your original example before moving the rest. Keep the original material until the transferred records and relationships are correct.
Read Work with GovCon MCP for document, company-matching, and pursuit limits. For direct data, bulk work, custom applications, or larger custom analysis, consider Tango by MakeGov. Professional G2X users receive 50% off any Tango plan. Contact G2X support for help applying the discount.