Time MCP Server Pricing 2026

Create crafted UI components inspired by the best 21st.dev design engineers.

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

The Linear MCP server connects your AI assistant directly to Linear's project management platform via an officially hosted remote endpoint at mcp.linear.app — no local installation required. This is Linear's own first-party server, authenticated with OAuth 2.1 and centrally managed so you always run the latest version without updates. Available tools let you search issues by keyword, team, cycle, or filter; create new issues with title, description, and assignee; update status, priority, labels, and comments; and navigate Linear's project and cycle structure. In Claude Code, add it with: `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`, then run /mcp to complete the OAuth flow. For older clients, use the mcp-remote bridge for backwards compatibility. Claude Desktop and Claude.ai users can connect via Settings > Connectors. Cursor and Codex have native support via their MCP config. Linear is used by thousands of engineering and product teams to plan, track, and ship software — the Linear MCP server brings that data into every AI-powered workflow without copy-paste or context-switching.

The HubSpot MCP Server is HubSpot's hosted, official Model Context Protocol endpoint for Smart CRM data, reachable at https://mcp.hubspot.com and authorised with OAuth 2.0 — there is no package to install and no token to paste into a config file. Access is scoped by a HubSpot user-level app: you create one with read (and optionally write) scopes for the CRM objects you want an assistant to reach, then complete the OAuth flow from inside your client. Read and write coverage spans contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions and lists, plus engagements — calls, emails, meetings, notes and tasks — and the associations between them. Organisational context (users, teams, reporting structures, owners, roles, seats) and marketing content (campaigns and their metrics, landing pages, website pages, blog posts) are read-only. Custom Sensitive Data Properties and Personal Health Information are excluded regardless of scopes. Two other things share the name and are commonly confused with this one: the Developer MCP server, installed locally with `hs mcp setup` from the HubSpot CLI and aimed at building HubSpot apps rather than querying CRM records, which requires Developer Platform v2025.2; and the original May 2025 public beta, an npm package configured with a private-app access token, which is what most third-party setup guides still describe. The server remains in beta and HubSpot advises experimenting in a developer sandbox and reviewing every write confirmation, since an LLM will occasionally propose a change to a system of record that it should not.

Agent-driven builds, simulator runs, tests and debugging for iOS and macOS projects, by wrapping xcodebuild, simctl and the device tooling behind MCP. The project is XcodeBuildMCP, and the first thing to know about it is that it moved: the repository that most write-ups still link, `cameroncooke/XcodeBuildMCP`, now redirects to `getsentry/XcodeBuildMCP` — Sentry took stewardship, and the canonical package, docs site and Homebrew tap all live under that org. At 6,172 stars it is the most-adopted Xcode MCP server by a wide margin. It ships as one package with two modes off the same install: an MCP server for agents (`xcodebuildmcp mcp`, or on demand via `npx -y xcodebuildmcp@latest mcp` with no global install) and a plain CLI for terminal use (`xcodebuildmcp simulator build --scheme MyApp --project-path ./MyApp.xcodeproj`, `xcodebuildmcp tools`, `xcodebuildmcp upgrade --check`). Install with Homebrew (`brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp`) or npm (`npm install -g xcodebuildmcp@latest`); Homebrew is the path that does not require Node. Beyond build-and-run it covers the workflow steps agents usually cannot reach — booting and driving simulators, capturing logs through a per-workspace daemon that auto-starts for stateful operations, and splitting test builds from test runs via `--build-for-testing` and a portable `.xctestproducts` bundle so a prepared build can be executed later against a named simulator. It also installs optional agent Skills (`xcodebuildmcp init`) that prime the model on the tool surface — recommended for the CLI mode in particular. Requirements are strict and worth checking before you file a bug: macOS 14.5+, Xcode 16.x+, and Node 18+ unless you installed through Homebrew. Two behaviours to know up front: it asks xcodebuild to skip macro validation so Swift Macros projects do not fail the build, and device (as opposed to simulator) tools need code signing already configured in Xcode. Sentry is used for runtime error telemetry only, with documented opt-out. MIT licensed, TypeScript, actively maintained.

Anthropic's reference Model Context Protocol server for Google Drive — and a retired one, which is the first thing to know about it. The repository moved to modelcontextprotocol/servers-archived and was archived on 2025-05-28 with no commits since, while the npm package @modelcontextprotocol/server-gdrive stays published at 2025.1.14, so `npx @modelcontextprotocol/server-gdrive` still installs and runs without warning you. It is also much smaller than its reputation. The server exposes exactly one tool — `search`, which takes a query string and returns matching file names and MIME types. Everything else is MCP resources: files are addressed as `gdrive:///<file_id>`, with Google Workspace formats exported automatically (Docs to Markdown, Sheets to CSV, Presentations to plain text, Drawings to PNG) and all other file types served in their native format. Clients that do not surface resources well therefore look like the server is broken when it is behaving exactly as documented. Authentication is read-only by construction: the setup asks for the `https://www.googleapis.com/auth/drive.readonly` scope on an OAuth Client ID of type Desktop App, which means there is no tool here that can create, edit, move or reshare anything. The flow is manual — create a Google Cloud project, enable the Drive API, configure the consent screen, download the client key file, rename it to `gcp-oauth.keys.json` in the repo root, then run `node ./dist auth` once to write `.gdrive-server-credentials.json` beside it; a Docker path exists that mounts the key file and persists credentials in an `mcp-gdrive` volume. For maintained Drive access with writes, sharing controls and shared-drive support, the community server most teams move to is taylorwilsdon/google_workspace_mcp (PyPI `workspace-mcp`), which covers Drive as one of twelve Google Workspace services on a single connection. See the setup guide on this page for the full comparison.