Skip to main content

Manus Setup

note

Manus uses bearer token authentication via custom headers rather than browser-based OAuth. You'll need to generate a Civic token before connecting.

Prerequisites

Setup

  1. 1
    Generate a Civic Token

    Manus uses bearer token authentication rather than browser-based OAuth, so you'll need to generate a token in Civic first.

    1. Open app.civic.com and sign in
    2. Navigate to Install
    3. Click "Generate a Civic token" and copy it — you'll need this in the next step
  2. 2
    Add a Custom MCP Connector in Manus
    1. In Manus, open Settings → Connectors
    2. Click Add connectors → Custom MCP → Add custom MCP
    3. Select Direct configuration
    4. Enter the following as the server URL:
      https://app.civic.com/hub/mcp
    5. Click Add custom header and add:
      • Name: Authorization
      • Value: Bearer <YOUR_CIVIC_TOKEN>
    warning

    Manus does not have a dedicated bearer token field — all authentication is configured through custom headers. You must manually include the Bearer prefix (with a space) before your token. Entering the token alone will cause 401 errors.

    1. Save the connector. Civic MCP tools are now available in Manus.
  3. 3
    Test Your Connection

    Try these prompts to verify everything is working:

    "What MCP servers are available?"
    "Can you check my recent GitHub issues?"

Troubleshooting

Why do I keep getting 401 errors?

The most common cause is a missing or malformed Authorization header. Check that:

  • The header name is exactly: Authorization
  • The header value starts with: Bearer (with a space) followed by your token — not the token alone
  • Your Civic token hasn't expired — generate a new one from app.civic.com if needed
Can I use OAuth / browser authentication instead?

Browser-based OAuth is not currently supported in Manus's MCP connector. Token-based authentication via custom headers is the supported method.

Next Steps