Manus uses bearer token authentication via custom headers rather than browser-based OAuth. You’ll need to generate a Civic token before connecting.
Prerequisites
Manus Account
Access to Manus at manus.im
Civic Account
Create a free account and generate a token at app.civic.com
Setup
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.
- Open app.civic.com and sign in
- Navigate to Install
- Click “Generate a Civic token” and copy it — you’ll need this in the next step
Add a Custom MCP Connector in Manus
- In Manus, open Settings → Connectors
- Click Add connectors → Custom MCP → Add custom MCP
- Select Direct configuration
- Enter the following as the server URL:
- Click Add custom header and add:
- Name:
Authorization - Value:
Bearer <YOUR_CIVIC_TOKEN>
- Name:
- Save the connector. Civic MCP tools are now available in Manus.
Troubleshooting
Why do I keep getting 401 errors?
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?
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
Browse Available Servers
Explore what MCP tools Civic connects
Client Compatibility
See all supported clients and connection methods

