Planned AI connector
Bring governed BidAgent research and workflows into ChatGPT through MCP.
Learn how the planned BidAgent ChatGPT connector will expose controlled bid search, analysis, pursuit, and review tools through a secure remote MCP server.
Start with read-only tools
The first connector release should prioritize safe retrieval: search opportunities, inspect a pursuit, read analysis status, and fetch source-linked findings.
- Search opportunities
- Get pursuit summary
- Read compliance and evidence status
Protect tenant data with OAuth
Private tools require OAuth authorization, exact audience validation, scoped access, tenant checks, and useful 401 or 403 responses.
- Authorization code with PKCE
- Protected-resource metadata
- Per-tool scope enforcement
Keep writes approval-bound
Actions that create pursuits, request services, or modify records should require explicit authorization and user confirmation rather than silent execution.
- Read and write scope separation
- Approval annotations
- Audit evidence
Frequently asked questions
Is the ChatGPT connector live?
Not yet. The website documents the intended capability while the MCP transport, OAuth, rate limits, evaluations, and review controls are completed.
Will ChatGPT receive all company data?
No. The connector should expose only the minimum authorized data required by the selected tool, scope, tenant, and user action.