In-depth architectural comparison of the Joltsms MCP Server and Discourse MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Joltsms MCP Server
Communication · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Discourse MCP
Communication · Local stdio
Quality: 83/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Joltsms MCP Server if you need specialized Communication tools running via a local process. Choose Discourse MCP if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Joltsms MCP Server when:
You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: JOLTSMS_API_KEY, JOLTSMS_API_URL.
Provision dedicated real-SIM US phone numbers, receive inbound SMS, poll for messages, and extract OTP codes. Built for AI agents automating phone verification across platforms.
Official Discourse MCP server for forum integration. Search topics, read posts, manage categories and tags, discover users, and interact with Discourse communities.
Tools & Capabilities Breakdown
Joltsms MCP Server Tools (10)
joltsms_list_numbers
List active numbers with service labels, tags, and unread counts
joltsms_get_number
Full details for a single number
joltsms_update_number
Set service label, tags, or notes on a number
joltsms_provision_number
Rent a new dedicated real-SIM US number ($50/mo)
joltsms_release_number
Cancel/release a number at end of billing period
joltsms_list_messages
List recent SMS with parsed OTP codes
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Joltsms MCP Server is categorized under Communication and uses a local stdio subprocess. In contrast, Discourse MCP belongs to Communication using local stdio subprocess. Select Joltsms MCP Server when you need capabilities focused on communication and Discourse MCP when you require tools for communication.
Poll until an SMS arrives (key tool for OTP flows)
joltsms_get_latest_otp
Get the most recent parsed verification code
joltsms_billing_status
Check all subscriptions with billing health
Discourse MCP Tools (16)
discourse_select_site
Validate and select a Discourse site. Returns JSON with site URL and title.
discourse_search
Search site content. Returns JSON object with results array of matching topics (id, slug, title) and meta (total, has_more).
discourse_filter_topics
Discover 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_topic
Read 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_post
Read a specific post. Returns JSON with id, topic_id, post_number, username, created_at, and raw content.
discourse_read_topic_posts
Read 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_posts
Search 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_user
Get user info. Returns JSON with id, username, name, trust_level, created_at, bio, admin, and moderator.
discourse_list_user_posts
Get 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_users
List 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_messages
Get 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_draft
Retrieve a specific draft by key. Returns JSON with draft_key, sequence, and parsed data (title, reply, categoryId, tags, action).