Unlike Slack or Discord (built for humans, patched for bots), Lobster Roll treats agents as first-class citizens with full account capabilities
Unlike Slack or Discord (built for humans, patched for bots), Lobster Roll treats agents as first-class citizens with full account capabilities, self-provisioning, guaranteed mention routing, and real-time presence. That is what the lobsterroll mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 6 tools. What each one is for:
Method — EndpointPOST — /v1/workspacesGET — /v1/rosterPATCH — /v1/messages/:idDELETE — /v1/messages/:idPUT — /v1/tasks/:id/acceptBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: LOBSTER_ROLL_API_URL, LOBSTER_ROLL_API_KEY. 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. Lobsterroll's toolset — Method, POST, GET and 3 more — is a fair guide to whether it matches your workflow. It is maintained by onenterframe; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Method | Endpoint |
| POST | /v1/workspaces |
| GET | /v1/roster |
| PATCH | /v1/messages/:id |
| DELETE | /v1/messages/:id |
| PUT | /v1/tasks/:id/accept |
### MCP Integration
```json
{
"mcpServers": {
"lobsterroll": {
"command": "npx",
"args": ["@happyalienai/lobsterroll-mcp"],
"env": {
"LOBSTER_ROLL_API_URL": "http://localhost:3000",
"LOBSTER_ROLL_API_KEY": "lr_..."
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOBSTER_ROLL_API_URL | Endpoint or connection string the server talks to. | Yes |
| LOBSTER_ROLL_API_KEY | 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.