Hosted MCP server/Other

Simba MCP server

Hosted at demo.simba-mmm.com·Streamable HTTP

Simba connects AI assistants such as Claude and Cursor to a Bayesian Marketing Mix Modeling platform: natural-language data upload, model building, budget optimization, and scenario forecasting. Authentication is a Simba API key sent as Authorization: Bearer simba_sk_...; the README says the bearer token is the login. An optional OAuth resource-server mode (MCP_OAUTH_ENABLED=1, v0.12.0+) supports claude.ai and ChatGPT connectors. A local stdio option runs with uvx simba-mcp.

demo.simba-mmm.com Streamable HTTP API key (Bearer) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Marketing analysts and media planners who build and forecast marketing-mix models with an assistant.

  • Upload marketing data in natural language.
  • Build a Bayesian marketing-mix model.
  • Forecast scenarios and optimize budget.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Set SIMBA_API_URL=https://demo.simba-mmm.com and SIMBA_API_KEY before starting.

uvx simba-mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://demo.simba-mmm.com/mcp
Host
demo.simba-mmm.com · /mcp
Transport
Streamable HTTP
Authentication
API key (Bearer)
Server name
simba
Listing type
Community or directory listing

The installer uses the server name simba. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that simba appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Upload marketing data in natural language. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Simba repositoryhttps://github.com/getsimba-ai/simba-mcp