Something else

Any other MCP client

For Cursor, Zed, Goose, Cline, n8n, or anything else that speaks MCP — point it at https://croft.now/mcp over Streamable HTTP. We don't know your client's UI, so there are no steps here, only the facts.

Back

Needs An MCP client that speaks Streamable HTTP and OAuth 2.1 with PKCE (S256).

What happens next

Croft authenticates with OAuth 2.1, PKCE (S256), and dynamic client registration (RFC 7591) for clients that register themselves, or CIMD for clients that identify by a fixed URL instead — there is no API key to paste either way. Whether your client supports resources and elicitation depends on the client itself; assume neither until you've checked, and if it turns out yours lacks resources, the read path is the read_resource tool, which takes a croft:// URI.

Check it worked

One row per workspace you can open, each carrying its {org}/{workspace} scope string, from the croft://workspaces resource (or via read_resource if your client doesn't support resources). Getting it back proves discovery, registration, the OAuth round trip and the token all worked in one move.

It only looks things up in Croft when you ask it to.

It can't stop partway through to ask you a question. If a workflow needs a setting you haven't given, Croft adds it paused and lists what's missing.

If it didn't

The client can't complete OAuth against Croft at all.

It expects dynamic client registration and doesn't support CIMD, or the reverse — this varies by client and isn't something Croft can detect from its side.

Check your client's docs for which of RFC 7591 dynamic registration or CIMD (fixed client URL) it supports; Croft's authorization server accepts both.

A tool call returns "not found" for a workspace you know exists.

Croft is looking at a workspace this connection can't reach — it was authorized under a different account than the one that workspace belongs to, or you've been removed from it since.

Check which account the connection was authorized with.

Verified 16 Sep 2026