Mdshare vs Temporal Cortex MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mdshare vs Temporal Cortex MCP
In-depth architectural comparison of the Mdshare and Temporal Cortex 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
Mdshare
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Temporal Cortex MCP
Workplace & Productivity · Local stdio
Quality: 65/100 (Great) | Auth: other
Verdict Summary: Choose Mdshare if you need specialized Workplace & Productivity tools running via a local process. Choose Temporal Cortex MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mdshare when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Markdown collaboration for AI workflows. Share markdown instantly via public links with four permission levels (admin, edit, comment, view), inline comments anchored to text, real-time WebSocket sync, and version history. Free, no login. npx mdshare-mcp lets AI agents read docs, review comments, incorporate feedback, and resolve threads — the full review loop without copy-pasting between tools.
AI-native calendar middleware for scheduling, availability, and conflict-free booking across Google Calendar, Outlook, and CalDAV. 15 tools across 5 layers: temporal context, calendar operations, multi-calendar availability, open scheduling, and Two-Phase Commit booking. Deterministic datetime resolution and RRULE expansion powered by Truth Engine.
Tools & Capabilities Breakdown
Mdshare Tools (14)
upload_markdown
Upload markdown to mdshare and receive a shareable link. The response contains a read/comment/edit share link (default permission: comment) that the user can share with others. The admin credential (full control) is stored locally in ~/.mdshare-mcp/documents.json and is NOT returned in this response — if the user explicitly asks to see or save the admin URL, call get_admin_url. PREFER file_path over content for files already on disk — reads directly from disk without transmitting content through this conversation, which is dramatically faster for files larger than ~1KB.
read_document
Read a markdown document from mdshare. Returns the content. If the document was uploaded via this MCP server, 'key' is optional — the admin key will be loaded from local storage. PREFER output_path over inline reading for large documents — writes directly to disk and returns a small summary, dramatically faster than echoing content through the conversation.
update_document
Update the content of an existing mdshare document (full replace). Requires edit or admin permission. If the document is in this MCP server's local store, 'key' is optional. PREFER file_path over content for files already on disk — reads directly from disk without transmitting content through this conversation. If both file_path and content are provided, file_path wins. For small edits to large documents, consider patch_document instead — keeps version history granular.
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).
Mdshare is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Temporal Cortex MCP belongs to Workplace & Productivity using local stdio subprocess. Select Mdshare when you need capabilities focused on workplace & productivity and Temporal Cortex MCP when you require tools for workplace & productivity.
Apply find/replace operations to a document without rewriting the full content. More efficient than update_document for small edits to large documents. Each find string must be unique unless replace_all is set. If the document is in this MCP server's local store, 'key' is optional. PREFER file_path over operations for batches of operations stored in a JSON file on disk — bypasses inline transmission. If both file_path and operations are provided, file_path wins.
generate_link
Generate a share link for a document with specific permissions. Requires admin access. If the document is in this MCP server's local store, 'key' is optional.
list_links
List all share links for a document, including status (active/revoked), permission, and label. Requires admin access. If the document is in this MCP server's local store, 'key' is optional.
revoke_link
Revoke a share link, making it permanently inactive. Use list_links first to find the token of the link to revoke. Requires admin access. If the document is in this MCP server's local store, 'key' is optional.
list_comments
List all comments on a document, including replies and resolution status. If the document is in this MCP server's local store, 'key' is optional.
post_comment
Post a comment on a document, optionally anchored to specific text. Can also reply to an existing comment. If the document is in this MCP server's local store, 'key' is optional.
resolve_comment
Resolve or unresolve a comment. Requires edit or admin permission. Key must be provided explicitly because comments are addressed by comment_id — the MCP server can't look up the parent document.
get_versions
Get the edit history of a document — who edited, when, and via what. If the document is in this MCP server's local store, 'key' is optional.
list_my_documents
List documents you've previously uploaded via this MCP server on this machine. Returns document_id, title, share_url, share_permission, created_at, and expires_at for each — does NOT return the admin credential. Use this to help the user find and resume older documents without re-pasting admin URLs. Does NOT include documents created via the mdshare web UI or via direct API calls from other clients — only those created by this MCP server. Returns an empty array on a fresh install or after the local store has been cleared.
+2 more tools listed on main page
Temporal Cortex MCP Tools (18)
adjust_timestamp
Adjust a timestamp by adding or subtracting a duration. DST-aware: '+1d' preserves wall-clock time across daylight saving transitions.
book_slot
Book a calendar slot using Two-Phase Commit for safe, conflict-free booking.
check_availability
Check if a calendar time slot is available (not held by another booking).
compose_proposal
Compose a scheduling proposal message with proposed time slots. Formats times in the specified timezone for email, Slack, or SMS. Does NOT send the message — returns formatted text for the agent to send via its channel MCP (Gmail, Slack, etc.).
compute_duration
Compute the duration between two timestamps. Returns days, hours, minutes, seconds, and a human-readable string.
convert_timezone
Convert a datetime to a different timezone.
expand_rrule
Expand a recurrence rule (RRULE) into concrete event instances.
find_free_slots
Find available free time slots in a calendar within a time window.
get_availability
Get unified availability across multiple calendars. Merges events from all specified calendars into a single busy/free view with privacy controls.
get_temporal_context
Get the current temporal context — time, timezone, calendar metadata. Call this first to orient yourself in time before making calendar queries.
list_calendars
List all connected calendars across providers. Returns calendar IDs, names, labels, and metadata. Call this first to discover what calendars are available before using other calendar tools.
list_events
List calendar events in a time range. Returns events in TOON or JSON format.