Skip to main content

​
ChatGPT MCP is not supported today

SEC API has not published or verified a ChatGPT MCP connection. Do not add https://api.secapi.ai/mcp to a Custom GPT or ChatGPT app and expect it to work as an SEC API integration. SEC API publishes OAuth protected-resource metadata and authorization-server metadata. That discovery metadata is not sufficient evidence of ChatGPT compatibility: the live MCP POST tool-discovery path returns an ApiKey WWW-Authenticate challenge. ChatGPT cannot provide a custom API key for that MCP connection. SEC API will publish setup instructions only after the MCP tool-call authentication challenge is OAuth-compatible and the full connection has been verified in ChatGPT.

​
Use one of these supported paths instead

For a developer-owned desktop workflow, use Continue. For a server-side integration, use LangChain, LlamaIndex, or the Vercel AI SDK. Those clients can keep an SEC API credential in a local developer secret store or in server-side infrastructure you control. Do not place it in a ChatGPT configuration.

​
Why the discovery documents are not enough

OAuth discovery metadata identifies the authorization server and its advertised grant capabilities. It does not establish that a particular MCP client can complete the required authorization challenge. Check this page again after SEC API publishes a verified ChatGPT compatibility result.

​
OpenAPI Actions are separate

ChatGPT Actions are a separate OpenAI product surface from MCP tool discovery. This page does not document an SEC API Action configuration or treat Actions as a workaround for the unsupported ChatGPT MCP connection. Review OpenAI’s current Action requirements before evaluating an Action independently.