RaiseKit

co.raisekitPublished by raisekit.coOfficial publisherv0.1.0Updated Oct 24, 2026

CRM for VC fundraising. Pipeline, Gmail drafts, deck signals, VC intel — from your AI.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote CRM for venture fundraising that lets an assistant work with your investor pipeline, Gmail drafts, deck signals and VC intelligence.

What you can do
RaiseKit is a hosted CRM aimed at venture-capital fundraising. Connected through a remote MCP endpoint, it lets an assistant work with your fundraising pipeline, Gmail drafts, deck signals and VC intelligence. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Consider it if you are raising a round and want an AI assistant to help manage investor pipeline and outreach from a fundraising CRM rather than a general-purpose one.
Requirements
A remote MCP endpoint at raisekit.co over streamable HTTP. A RaiseKit account and an agent token are required, sent as a bearer token in the Authorization header. No local runtime or environment variables are declared.
Before you install
The Authorization header carries a bearer agent token, which grants access to your fundraising CRM data; treat it as a secret and revoke it if exposed. The server can involve Gmail drafts and outreach, so check what it sends or creates before enabling it. Data is held by a third-party service.

Installation

In SourceWeft

  1. Open RaiseKit in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/co.raisekit%2Fraisekit/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.

{
  "mcpServers": {
    "raisekit": {
      "type": "http",
      "url": "https://raisekit.co/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

56% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.