FortyOne for developers and agents
Build from a documented, machine-readable surface.
Discover the public FortyOne API contract, agent-readable content, and Model Context Protocol endpoint. Authenticated product data remains governed by workspace and team permissions.
OpenAPI 3.1
Inspect typed public endpoints, unique operation IDs, response schemas, and authentication requirements.
View OpenAPI JSONModel Context Protocol
Connect ChatGPT, Claude, Cursor, Codex, and other MCP clients to permission-aware FortyOne tools.
View MCP metadataProduct documentation
Read guides for FortyOne product concepts, workflows, integrations, and workspace administration.
Read the docsAuthentication boundary
The remote MCP server uses a separate FortyOne OAuth connection with PKCE, audience-bound tokens, refresh-token rotation, revocation, and an explicit consent screen. Every tool runs as the connected user and reuses existing workspace and team permission checks. Create tools also require explicit user confirmation.