AgentLair vs Discourse MCP
A side-by-side look at the AgentLair and Discourse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AgentLair for communication work as a local process; choose Discourse MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AgentLair when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AGENTLAIR_API_KEY, AGENTLAIR_EMAIL. - You want tools like
claim_address, send_email, check_inbox.
Choose Discourse MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
discourse_select_site, discourse_search, discourse_filter_topics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 60/100 · Good | 87/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | AGENTLAIR_API_KEYAGENTLAIR_EMAIL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 5 | 77 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 15 | 16 |
| Full listing | View AgentLair | View Discourse MCP |
Tools & capabilities
AgentLair tools 15
claim_addressClaim a new @agentlair.dev email address for your agent. No DNS or SMTP setup required. Free tier: up to 3 addresses.send_emailSend an email from an @agentlair.dev address you own to any recipient. No SMTP setup needed.check_inboxCheck the inbox for an @agentlair.dev address. Returns recent messages with sender, subject, and received time.read_messageRead the full content of a specific email message, including the body. Use message IDs from check_inbox.list_addressesList all @agentlair.dev addresses claimed on your account.vault_putStore a value in the AgentLair Vault. Use this to persist API keys, secrets, or any data your agent needs across sessions. Best practice: encrypt sensitive data client-side before storing (the server stores whatever you send).vault_getRetrieve a stored value from the AgentLair Vault by key name.vault_listList all keys stored in your AgentLair Vault (metadata only, values not returned).vault_deleteDelete a key and all its versions from the AgentLair Vault.calendar_create_eventCreate a calendar event on your AgentLair calendar. Events are published via iCal feed for human subscription (Google Calendar, Apple Calendar, Outlook).calendar_list_eventsList events on your AgentLair calendar. Optionally filter by date range.calendar_delete_eventDelete an event from your AgentLair calendar by event ID. Use calendar_list_events to find event IDs.- +3 more on the listing page
Discourse MCP tools 16
discourse_select_siteValidate and select a Discourse site. Returns JSON with site URL and title.discourse_searchSearch site content. Returns JSON object with results array of matching topics (id, slug, title) and meta (total, has_more).discourse_filter_topicsDiscover topics through a filtered, top, or hot view. Filtered uses Discourse TopicsFilter syntax; top uses Discourse's authoritative top score and defaults to weekly; hot is defined exactly as daily top (not sentiment, controversy, or real-time velocity). Returns a uniform rich topic projection and truthful pagination metadata.discourse_read_topicRead topic metadata and posts. Large post limits can require multiple upstream requests. For moderation queues, prefer reviewable list/detail evidence instead of fanning this tool out across flagged topics.discourse_read_postRead a specific post. Returns JSON with id, topic_id, post_number, username, created_at, and raw content.discourse_read_topic_postsRead exact, earliest, latest, around-post, or username-filtered topic evidence. Selection is bounded to 50 posts and reports the visible stream size without claiming the entire topic was loaded.discourse_search_postsSearch post-level evidence with Discourse query syntax. Unlike discourse_search, this preserves matched posts, highlighted blurbs, authors, topics, categories, and truthful bounded continuation. This is keyword search, not Discourse AI semantic search.discourse_get_userGet user info. Returns JSON with id, username, name, trust_level, created_at, bio, admin, and moderator.discourse_list_user_postsGet paginated list of user posts/replies. Returns JSON object with posts array (id, topic_id, post_number, slug, title, created_at, excerpt, category_id) and meta (page, limit, has_more).discourse_list_usersList users via admin API. Requires admin API key. Returns ~100 users per page (Discourse's fixed page size). Returns JSON with users array and pagination meta.discourse_get_chat_messagesGet messages from a chat channel. Returns JSON object with channel_id, messages array (id, username, created_at, message, edited, thread_id, in_reply_to_id), and meta.discourse_get_draftRetrieve a specific draft by key. Returns JSON with draft_key, sequence, and parsed data (title, reply, categoryId, tags, action).- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AgentLair
{
"mcpServers": {
"agentlair": {
"command": "npx",
"args": [
"-y",
"@agentlair/mcp@latest"
],
"env": {
"AGENTLAIR_API_KEY": "YOUR_AGENTLAIR_API_KEY_HERE",
"AGENTLAIR_EMAIL": "YOUR_AGENTLAIR_EMAIL_HERE"
}
}
}
}
Discourse MCP
{
"mcpServers": {
"discourse-discourse-mcp": {
"command": "npx",
"args": [
"-y",
"@discourse/mcp@latest"
]
}
}
}
Frequently asked questions
AgentLair is categorized under Communication and uses a local stdio subprocess. Discourse MCP belongs to Communication and uses a local stdio subprocess. Pick AgentLair for communication work and Discourse MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AgentLair has no declared pricing — check the project's own site. Discourse MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agentlair and discourse-discourse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentLair has a quality signal of 60/100 (Good) with 2 views, 0 installs and 5 GitHub stars. Discourse MCP has 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars.