Person Enrichment API vs Slack MCP Server

In-depth architectural comparison of the Person Enrichment API and Slack MCP Server 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.

Which MCP Server Should You Choose?

Choose Person Enrichment API when:

• You need dedicated capabilities in the Communication domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: person_enrich_from_email, email.

Explore Person Enrichment API Details

Choose Slack MCP Server when:

• You need dedicated capabilities in the Communication domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: other (Free / Open Source).
• You have access to required keys: SLACK_MCP_ADD_MESSAGE_TOOL.
• Primary tools included: UserID, UserName, RealName.

Explore Slack MCP Server Details

Feature & Specification Comparison

Specification	Person Enrichment API Communication	Slack MCP Server korotovsky Communication
Summary	Person lookup from email: name, title, company, social profiles. x402.	The most powerful MCP server for Slack Workspaces.
Category & Scope	Communication	Communication

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "person-enrichment-api": {
      "url": "https://person-enrichment.api.klymax402.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "korotovsky-slack-mcp-server": {
      "url": "https://api.slack.com/changelog/2023-07-its-later-already-for-stars-and-reminders"
    }
  }
}

Related MCP Server Comparisons