Updated October 22, 2026

MCP servers
you can connect to your workflow

Need repository context, workspace knowledge or Stripe tools in your assistant? Compare three official servers below, then use the provider’s instructions for your client. This is a documentation review, checked on 22 October 2026; ClawSites has not tested these connections.

Browse the official MCP registry Explore agents and tools Read the AI agents guide

Short answer

An MCP server exposes tools or context to an MCP client, such as a compatible coding assistant. Choose the service whose data you need, check that your client supports its connection and authentication, then inspect the tools and permissions before using it. A framework or server directory is not itself the server you connect.

Four checks before connecting

The task

Pick the service that owns the context or action your workflow needs. Do not install overlapping servers just to expand a tool list.

The connection

Check whether the server is hosted or runs locally, and follow the transport and setup documented for your client.

The account

Identify which user or token grants access and which resources it can reach. A successful connection does not establish the right scope.

The result

Start with a task you can verify, such as reading one known record. Check the returned source and available tools before enabling changes.

Match the server to the work

GitHub: give a coding assistant repository, issue and pull-request context.
Notion: find and work with knowledge in a connected workspace.
Stripe: inspect Stripe resources or search its documentation from a compatible assistant.

Choose a starting point

Situation	Recommendation
You need GitHub context without changing a repository	Review GitHub’s read-only configuration and the account permissions before selecting toolsets.
You need Notion workspace content	Use Notion’s hosted service and its current client-specific connection guide. Confirm which workspace content the connecting account can access.
You are exploring Stripe operations	Use a sandbox and inspect the allowed tools. Stripe exposes read and write operations; a connection is not inherently read-only.

Official servers and setup

GitHub MCP Server: repositories and development work

GitHub maintains a remote server at https://api.githubcopilot.com/mcp/ and local Docker or binary options. The hosted connection uses HTTP; local configurations use stdio. The repository includes setup guides for clients such as VS Code, Claude Code, Claude Desktop and Cursor.

Authentication options depend on the client. The provider documents OAuth and personal access tokens, plus toolset selection and a read-only mode. Account and token permissions still apply. GitHub Enterprise Server needs its own documented configuration; do not assume that the GitHub-hosted endpoint covers it.

GitHub MCP setup and client guides GitHub remote configuration and read-only mode

Notion MCP: workspace knowledge and documents

Notion’s hosted server connects at https://mcp.notion.com/mcp using Streamable HTTP. Its documentation covers searching workspace content and reading, creating or updating pages and databases. Setup instructions are available for Codex, Claude Code, Cursor and VS Code, among other clients.

OAuth connects a user’s workspace access. Workspace permissions and plan-specific controls remain relevant; guests cannot connect. Use the current hosted-service guide rather than an old local-package tutorial: Notion says its local notion-mcp-server package is no longer actively maintained.

Connect to Notion MCP Notion MCP capabilities and access

Stripe MCP: documentation and Stripe resources

Stripe offers a hosted server at https://mcp.stripe.com. Its HTTP setup examples cover Cursor, Claude, Codex and VS Code. Tools include documentation search and work with resources such as customers, invoices and subscriptions.

The current guide uses OAuth for user-authorized access or agent API keys for independent access. Permissions can differ between live accounts and sandboxes. Review the tool list and start in a sandbox; check the provider’s current authentication guidance instead of copying an older key example.

Stripe MCP setup, authentication and tools

Check one connection before expanding it

These steps are a suggested evaluation method, not a completed ClawSites benchmark. Use the setup link for your exact client and account. If it lacks the required transport or authentication support, choose another documented client or connection option.

List the resources the connecting identity can access and the tools exposed to the assistant.
Ask for one known record that the account is allowed to read. Check that the returned content matches the source.
If changes are needed, first use a disposable record or sandbox and inspect the resulting state in the service.
Record the client, server configuration, date and limits of the test. Recheck permissions when the workflow or tools change.

Compare the connection models

These are documented options, not a ranking or a guarantee of compatibility. The provider links above are the source of truth for current setup.

Official server	Connection and task	Authentication and access
GitHub MCP Server	Remote HTTP or local stdio; repositories, issues and pull requests.	OAuth or PAT options depend on the client; account permissions, toolsets and read-only configuration apply.
Notion MCP	Hosted Streamable HTTP; workspace search and documents.	OAuth and workspace permissions; check client and plan requirements. Guests cannot connect.
Stripe MCP	Hosted HTTP; documentation and Stripe resources.	OAuth or agent API keys; inspect read/write tools and distinguish sandbox from live-account permissions.

Keep servers, clients and directories distinct

The server provides tools or context. Your client decides how the assistant uses them. A directory helps you discover servers, and a gateway may manage several integrations. These roles can appear in the same product, but they are not interchangeable setup instructions.

An official server still needs an appropriate account and permissions. The comparisons here do not establish runtime reliability, total cost or support for every client version. Consult the linked provider documentation for those decisions.

Browse the official MCP registry

Continue with official setup or broader discovery

GitHub MCP Server Notion connection guide Stripe MCP documentation Official MCP registry Browse agents and tools

Choosing an MCP server

Do I need to install every MCP server locally?

No. This selection includes hosted connections, and GitHub also documents local options. Follow the setup for your server and client rather than assuming that every connection needs a local process.

Does connecting an MCP server make it read-only?

No. Access depends on the service, identity and exposed tools. Check the documented permission controls and tool list before allowing changes.

Has ClawSites tested these connections?

No. This comparison is based on official documentation reviewed on 22 October 2026. It does not claim measured speed, reliability or compatibility with every client version.

Choose the server for one task

Use an official setup guide to check your client and account. If you are still choosing the agent itself, explore the directory by task and product type.

Browse the official MCP registry Explore agents and tools

MCP servers you can connect to your workflow