Seeder

so.seederPublished by seeder.soOfficial publisherv0.8.0Updated Oct 24, 2026

Search and act on your VC firm's deal pipeline: deals, notes, tasks, analyst assignment.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search and act on a venture capital firm's deal pipeline, including deals, notes, tasks and analyst assignment.

What you can do
Seeder connects an assistant to a VC firm's deal pipeline. According to the description, it lets the assistant search and act on deals, notes, tasks and analyst assignment. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful for venture capital teams that keep their deal pipeline in Seeder and want an assistant to look up deals, notes or tasks and take action on them without switching tools.
Requirements
A remote MCP endpoint at app.seeder.so using streamable HTTP. Authentication is OAuth and required, so a Seeder account with access to the firm's pipeline is needed. No environment variables or headers are declared.
Before you install
The server can act on pipeline data, not just read it, so changes to deals, notes, tasks and analyst assignments may be made on the assistant's behalf. Access is tied to an OAuth account with visibility into the firm's deal data. Review what actions are permitted before connecting.

Installation

In SourceWeft

  1. Open Seeder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/so.seeder%2Fdms/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "seeder": {
      "type": "http",
      "url": "https://app.seeder.so/api/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.8.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.