Skip to content

Developer resources

Everything you need to build.

Your permissions stay in place.

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.

Ready to bring strategy, feedback, and work together?