Top API integration MCP servers

Ranked by the composite AgentRank score — a weighted blend of stars (15%), freshness (25%), issue health (25%), contributors (10%), and inbound dependents (25%). Average score across all 876 API integration tools is 28.9. The tools below are the top tier.

Choosing by use case

Google Workspace (Gmail, Calendar, Docs, Sheets)

taylorwilsdon/google_workspace_mcp is the top-scoring API integration tool at 90.94. It covers the full Google Workspace surface — Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms, and Tasks — from a single server. 78 contributors and active commits through mid-March 2026. If your agent needs to interact with any Google productivity tool, this server covers it.

GitHub

github/github-mcp-server is GitHub's official MCP server, scoring 85.44 with 27,865 stars and 111 contributors — the most-starred API integration server in the entire index. Issues, pull requests, repositories, code search, actions — all exposed through MCP. For any agent workflow that touches GitHub, this is the only server worth considering.

Slack

korotovsky/slack-mcp-server scores 83.01 with 1,448 stars and 40 contributors. The standout feature is that it works without elevated Slack app permissions — most Slack MCP servers require broad OAuth scopes that workspace admins resist approving. This one is designed to work with standard user-level access, making actual deployment far less painful.

Git repositories (remote, any host)

idosal/git-mcp takes a different approach: it's a remote MCP server (score 75.44, 7,759 stars) that serves any public GitHub or GitLab repository over the wire without local setup. The original problem it solves is code hallucinations — give an agent access to the actual repo source instead of its training data. Useful for agents that need to reference external libraries, documentation repos, or any codebase they don't own locally.

Notion

makenotion/notion-mcp-server is the official server from Notion, scoring 74.87 with 4,039 stars and 22 contributors. Active through March 2026. It covers pages, databases, blocks, and search. If your team's knowledge base lives in Notion, this server gives agents the same access a human has through the Notion UI.

Airtable

domdomegg/airtable-mcp-server scores 74.68 with 428 stars and 10 contributors, last committed March 7, 2026. It's the best Airtable integration in the index — lets agents read and write records, query views, and manage bases. Airtable is often the database of choice for non-engineering teams, making this a useful bridge between agents and operational data that lives outside engineering tooling.

Atlassian (Jira + Confluence)

sooperset/mcp-atlassian covers both Jira and Confluence from one server, scoring 72.75 with 4,608 stars and 96 contributors — the second-highest contributor count in this list. If your engineering org runs on Atlassian, this server connects agents to your issue tracker and wiki simultaneously. The Atlassian team also maintains their own official server (atlassian/atlassian-mcp-server at 71.88), but the community server currently scores higher due to stronger contributor activity.

What to watch for

Official vs community servers

Three of the top seven are official servers: GitHub, Notion, and the Atlassian team. Official servers track API version changes and deprecations — critical for external APIs that change without warning. In the Atlassian case, the community server (sooperset/mcp-atlassian) currently outscores the official one on contributor activity, but both are worth tracking.

OAuth and permissions complexity

API integration servers require OAuth setup in ways that database or file servers don't. Slack in particular has a notoriously complex permissions model — it's why korotovsky/slack-mcp-server's "no elevated permissions" design is a meaningful differentiator, not just a feature. Before depending on any integration server, audit what OAuth scopes it requires and whether your workspace or org admin will approve them.

Rate limits hit differently with agents

Agents make API calls at machine speed. A GitHub MCP server used by an agent running in a loop can exhaust the GitHub API rate limit (5,000 requests/hour for authenticated users) in minutes. Build rate limit handling — backoff, caching, request batching — into your agent workflows, not into the MCP server after the fact.

The category has the most competition

API integration has 876 tools in the index — by far the largest category. That means more choices, but also more abandoned forks and stale clones. The average score across the category is 28.9, compared to 32.5 for data science. Use the AgentRank score to cut through the noise — it surfaces maintainer quality and freshness rather than raw star counts.

Methodology

Tools classified as "API integration" via keyword matching on description, topics, and repo name — covering Slack, GitHub, Notion, Google Workspace, Google Drive, Gmail, Jira, Confluence, Airtable, Linear, Zapier, n8n, and related SaaS tool names. Only non-archived repositories with a computed score included. Data from the AgentRank index crawled March 2026.

Score weights: stars 15%, freshness (days since last commit) 25%, issue health (closed/total ratio) 25%, contributors 10%, inbound dependents 25%.