MCP server for Tangerine (Convo AI assistant backend): https://github.com/RedHatInsights/tangerine-backend
Tangerine MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Tangerine MCP directly instead of describing what you should do. MCP server for Tangerine (Convo AI assistant backend): https://github.com/RedHatInsights/tangerine-backend.
You will need 3 environment variables: TANGERINE_URL, TANGERINE_TOKEN, MCP_TRANSPORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by redhat-ai-tools; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"tangerine": {
"command": "podman",
"args": [
"run",
"-i",
"--rm",
"-e", "TANGERINE_URL",
"-e", "TANGERINE_TOKEN",
"-e", "MCP_TRANSPORT",
"quay.io/maorfr/tangerine-mcp:latest"
],
"env": {
"TANGERINE_URL": "https://tangerine.example.com",
"TANGERINE_TOKEN": "REDACTED",
"MCP_TRANSPORT": "stdio"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TANGERINE_URL | Endpoint or connection string the server talks to. | Yes |
| TANGERINE_TOKEN | Credential the server authenticates with. | Yes |
| MCP_TRANSPORT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.