Skip to content
famasi.ai

Generic

Connect any MCP-compatible client to Famasi’s provider API. This is the minimal setup — just a .mcp.json configuration file pointing to the Famasi MCP server. No agent files, no skill files.

Install

Terminal window
npx @famasi/agents@latest install generic-mcp

Configuration

Basic connection:

{
  "mcpServers": {
    "famasi-provider": {
      "url": "https://mcp.famasi.ai/mcp"
    }
  }
}

With API key:

{
  "mcpServers": {
    "famasi-provider": {
      "url": "https://mcp.famasi.ai/mcp",
      "headers": {
        "x-api-key": "pk_live_..."
      }
    }
  }
}

Authenticate

Terminal window
# Set API key via environment variable (recommended)
export FAMASI_PROVIDER_API_KEY=pk_live_...


# Or persist key in .mcp.json during install
npx @famasi/agents@latest install generic-mcp --provider-api-key pk_live_... --persist-secrets


# Link your provider identity
npx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_ID

Full authentication details →

Available tools

All 26 provider tools plus 2 documentation tools are available through the MCP server.

When to use this

Use generic-mcp when:

  • Your MCP client isn’t Claude Code or Codex
  • You want the minimal config (just .mcp.json)
  • You’re building a custom integration
  • You’re testing MCP connectivity

Use a specific target (claude-code, codex) when you want agent instructions and platform-specific behaviour like slash commands or AGENTS.md.

Troubleshooting

“Connection refused”

  • Verify the URL in .mcp.json is https://mcp.famasi.ai/mcp
  • Check your network can reach the endpoint

“Authentication failed”

  • Verify your API key is correct
  • Try npx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_ID to re-authenticate

“No tools available”

  • The MCP server exposes tools only after authentication
  • Check that x-api-key header is set in .mcp.json

More troubleshooting →