A Model Context Protocol (MCP) server for interacting with the Devici API. This server provides LLM tools to manage users, collections, threat
Connect Devici MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for interacting with the Devici API. This server provides LLM tools to manage users, collections, threat models, components, threats, mitigations, teams, and dashboard data through the Devici platform. The devici mcp mcp server is what makes that connection.
The server ships on PyPI as git, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Cline — The Cline tool exposed by this serverContinue — The Continue tool exposed by this serverCursor — The Cursor tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverSetup — The Setup tool exposed by this serverTesting — The Testing tool exposed by this serverBuilding — The Building tool exposed by this serverConfiguration is passed through the environment: DEVICI_API_BASE_URL, DEVICI_CLIENT_ID, DEVICI_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication 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. Devici MCP's toolset — Cline, Continue, Cursor and 4 more — is a fair guide to whether it matches your workflow. It is maintained by geoffwhittington; 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.
| Tool | What it does |
|---|---|
| Cline | The Cline tool exposed by this server. |
| Continue | The Continue tool exposed by this server. |
| Cursor | The Cursor tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | The Setup tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
| Building | The Building tool exposed by this server. |
#### Option 2: From PyPI (Future)
```json
{
"mcpServers": {
"devici": {
"command": "uvx",
"args": ["devici-mcp-server"],
"env": {
"DEVICI_API_BASE_URL": "https://api.devici.com/v1",
"DEVICI_CLIENT_ID": "your-client-id-here",
"DEVICI_CLIENT_SECRET": "your-client-secret-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DEVICI_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| DEVICI_CLIENT_ID | Configuration value read at startup. | Optional |
| DEVICI_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.