Other clients

Any Streamable HTTP-compatible AI client — such as Hatz, Grok, Gemini Enterprise, or Cursor — connects to Stackyapper’s Streamable HTTP endpoint:

1https://mcp.stackyapper.dev/mcp

Workspaces with a verified custom access domain use the origin shown on the portal’s AI clients page, keeping the /mcp path.

Interactive clients should use OAuth when available. Server-side integrations and automations that cannot open a browser can use a bearer API key created by the signed-in Stackyapper user.

Copilot Studio has its own guide.

Grok

In Grok Connectors, choose New Connector → Custom, name it Stackyapper, and enter https://mcp.stackyapper.dev/mcp. Complete the Stackyapper sign-in when prompted. These steps follow xAI’s custom connector setup.

If the sign-in page says approval is required, submit a request with a short explanation. An owner or admin reviews it under AI clients in Stackyapper. Keep the authorization window open. It checks for approval every five seconds for up to ten minutes, then continues to the connection consent screen. Finish approving the connection there. If the window expires, restart from Grok; a new registration may require a new approval. Seeing a list of tools alone does not confirm that your workspace is authenticated.

Grok Business and Enterprise administrators must first provision the connector for their organization. See organization-approved MCP servers.

Grok’s custom connection is reviewed as an individual OAuth registration. Its display name is not a verified publisher identity, and adding Grok here does not automatically approve it in your workspace.

Grok Bot

Grok Bot is separate from Grok on the web, Grok Build, and the xAI API. In Grok Bot, open Settings → Plugins to add a connection and complete browser authentication when requested, as described in xAI’s connection guide.

If your Grok Bot account offers a custom remote MCP connection, enter the Stackyapper endpoint above and start sign-in. If Stackyapper requires client approval, ask a workspace administrator to review the actual registration under AI clients before retrying. A display name such as “Grok Bot” does not verify the software publisher. Stackyapper treats this as a custom client, without an automatically trusted Grok product profile.

xAI’s Grok Bot guide does not specify a custom-server URL entry flow for every account. If that option is absent, use a supported client below or consult xAI about availability for your account. Do not paste a credential into a Bot chat. xAI documents that a user’s Bots share their computer, credentials, and installed connectors; a separate Bot name does not isolate access.

Other xAI clients

Grok web: custom connectors accept an MCP server URL under New Connector → Custom, followed by the requested authentication. Use the Stackyapper endpoint above.
Grok Build: its MCP setup guide supports remote HTTP servers and browser OAuth. Run grok mcp add --transport http stackyapper https://mcp.stackyapper.dev/mcp, then complete sign-in when prompted.
xAI API: remote MCP accepts a server URL and an authorization token. Use a Stackyapper API key belonging to a user with only the permissions the integration needs. Keep it in server-side secret storage. This is API automation, not Grok Bot sign-in.

API-key authentication

Create a client credential
In the Stackyapper portal, open AI clients → Connect and select New API key under Your direct API key.
Store the key securely
Copy the key when it is displayed. Stackyapper does not display the full value again.
Configure the client
Set the server URL to https://mcp.stackyapper.dev/mcp and provide the key as a bearer token.

Treat an MCP API key like a password. Do not put it in documentation, source control, client-side browser code, or screenshots.

Verify the connection

Most AI clients list a small set of stackyapper_ router and workflow tools — the expected surface, explained in What your AI client sees. Then run a read-only tool against an app you can read and confirm the call under Audit, following Connect a client and verify.