Other apps
Connect Assistant Core MCP from MCP clients without a dedicated guide, including local-only clients.
AI apps not covered in the previous pages can still connect if they support remote MCP. Look in the app's documentation for "remote MCP server", "custom connector" or "HTTP MCP server", and use the URL:
https://api.assistantcore.com/mcpMost apps accept JSON like:
{
"mcpServers": {
"assistant-core": {
"url": "https://api.assistantcore.com/mcp"
}
}
}The key name varies (url, serverUrl, httpUrl). If the app asks for a transport, choose Streamable HTTP (or HTTP), not SSE. If it asks for authentication, choose OAuth and leave Client ID and Client Secret empty.
Apps that only support local MCP
Some apps only run local (stdio) MCP servers declared with command. Use mcp-remote as a bridge; it needs Node.js:
{
"mcpServers": {
"assistant-core": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.assistantcore.com/mcp"]
}
}
}On first run, mcp-remote opens your browser to sign in to Assistant Core and stores the token in ~/.mcp-auth.
Technical requirements
For MCP client developers, or when checking why an app won't connect:
| Item | Value |
|---|---|
| Transport | Streamable HTTP (SSE is not supported) |
| URL | https://api.assistantcore.com/mcp |
| Auth discovery | 401 with WWW-Authenticate pointing to /.well-known/oauth-protected-resource/mcp (RFC 9728) |
| Authorization server | /.well-known/oauth-authorization-server (RFC 8414) |
| Flow | OAuth 2.1 Authorization Code + PKCE S256 |
| Client registration | Client ID Metadata Documents (client_id_metadata_document_supported), or Dynamic Client Registration (/oauth/register) for older clients. Metadata documents must describe a public client (token_endpoint_auth_method: none) |
| Redirect URI | HTTPS, http://localhost / 127.0.0.1, or a native app's private scheme. No fragments |
| Access token | Valid for 1 hour; refresh tokens rotate and expire after 30 days unused |
Apps that only accept a fixed API key (no OAuth) can't connect, because Assistant Core MCP doesn't issue API keys.
Connection troubleshooting
| Symptom | Fix |
|---|---|
| No browser window opens to sign in | Look for a Connect or Authenticate button, or a login command, in the app's MCP settings. Some apps only open it on the first tool call |
| Signed in but the app still reports an auth error | Use Clear authentication / Disconnect in the app's MCP settings, then connect again |
| The app reports a transport error | The app is using SSE. Switch to Streamable HTTP, or use mcp-remote |
| Connected but an assistant is missing | It wasn't selected when you granted access. Disconnect and connect again |
| The app runs on a remote server or over SSH | Sign-in needs a browser on the same machine as the app. Connect from your local machine |
For tool-call errors (FORBIDDEN, GRANT_SCOPE_REQUIRED…) see the Overview.