SourceWeft MCP Market

MCP Server Marketplace

Explore 35,116 MCP servers with tools, transport, auth, and trust details up front, then add them to a SourceWeft workspace.

Install

Add any listed server to a SourceWeft workspace in three steps.

  1. 1Pick a server and review its tools, auth, and trust level.
  2. 2Add it from the MCP page in your workspace dashboard.
  3. 3Connect credentials privately, then enable it for chats.
Sign in to install

Publish

List your own MCP server for every SourceWeft workspace.

  1. 1Publish your server source in a public GitHub repository.
  2. 2Submit the repository from the MCP page in the dashboard.
  3. 3It goes live after review; trusted publishers get a badge.
Sign in to submit

Featured

Servers from official publishers or verified by review.

View all

Recently updated

Freshly indexed servers and recently updated listings.

View all

AI & ML

LLM providers, agents, models, embeddings, inference, and machine learning workflows.

View all

Other

MCP servers that do not fit a primary SourceWeft category yet.

View all

Cloud & Infrastructure

Cloud providers, hosting, Kubernetes, Docker, Terraform, networking, deployment, and operations.

View all

Developer Tools

Code, Git, APIs, SDKs, CI/CD, developer workflows, and local developer tooling.

View all

Browse by category

MCP FAQ

MCP server basics

What is an MCP server?

An MCP server exposes tools and context through the Model Context Protocol, so an AI client can call external systems in a structured way.

How do I use an MCP server in SourceWeft?

Open the MCP server in SourceWeft, install it into a workspace, configure credentials if required, then enable it for chat runs from the dashboard.

Are unverified MCP servers safe?

Unverified MCP servers can receive tool arguments from a conversation and may perform external actions. Review the provider, tools, and requested credentials before enabling one.

What is the difference between HTTP/SSE and STDIO MCP?

HTTP and SSE MCP servers run remotely and can be used from web runtimes. STDIO MCP servers require a local desktop host because they start a local process.

Do MCP servers need API keys?

Some MCP servers require Bearer tokens, API keys, or custom headers. SourceWeft stores workspace credentials privately and does not expose them on public market pages.