FastMCP seed raise pipeline tracker — syncs from Obsidian CRM, generates meeting

io.github.adelaidasofiaPublished by GitHub account adelaidasofiav0.1.0Updated Oct 28, 2026

FastMCP seed raise pipeline tracker — syncs from Obsidian CRM, generates meeting prep, tracks…

The publisher's own server: Meeting.ai

Overview

AI-generated overview

FastMCP server that tracks a seed-round investor pipeline from Obsidian CRM notes, with meeting prep, interaction logging and follow-up analytics.

What you can do
  • Search and read the pipeline: find investors by name, stage, priority or days since last contact, and pull a full profile with interaction history
  • Generate meeting prep documents with portfolio fit, top objections and rebuttals, and a stage-appropriate agenda
  • Update records: change stage, log interactions, add investor-specific objections
  • Report pipeline health: stage breakdown, committed count and follow-up compliance
  • Re-sync the pipeline from Obsidian vault CRM markdown files
When to use it
For founders raising a seed round who keep investor notes as markdown in an Obsidian vault and want to manage the pipeline conversationally from Claude Code instead of a separate CRM.
Requirements
Runs locally as a stdio process (desktop only). Needs Python with fastmcp, pyyaml and python-frontmatter, or the packaged plugin install. Requires the CRM folder path via INVESTOR_MCP_VAULT_CRM (manifest lists VAULT_CRM_PATH), an optional SQLite path via INVESTOR_MCP_DB, and a filled-in pitch_config.yaml for meeting prep.
Before you install
Writes to your pipeline: stage changes, logged interactions and objections modify stored data, and sync reads your vault CRM files. The README states the plugin sends an anonymous install signal to an external site on first load per machine, including plugin name and version; set MYCELIUM_NO_PING=1 to opt out. pitch_config.yaml holds confidential pitch positioning and objection rebuttals.

Installation

In SourceWeft

  1. Open FastMCP seed raise pipeline tracker — syncs from Obsidian CRM, generates meeting in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

investor-relations-mcp

[License] [GitHub stars] [Last commit] [Open issues] [PyPI version] [PyPI downloads] [Built by Mycelium AI]

A FastMCP server for tracking your seed raise investor pipeline from Claude Code. Syncs from Obsidian vault CRM files, generates meeting prep documents, tracks interactions, and monitors follow-up compliance.

Built for founders raising a seed round who want to manage their pipeline conversationally without switching to a separate CRM.

Tools

ToolWhat it does
investor_searchSearch pipeline by name, stage, priority, or days since last contact
investor_profileFull investor profile + complete interaction history
investor_prepMeeting prep doc: portfolio fit, top 3 objections + rebuttals, stage-appropriate agenda
investor_updateUpdate stage, log interactions, add investor-specific objections
investor_analyticsPipeline health: stage breakdown, committed count, follow-up compliance
investor_syncRe-sync from vault CRM markdown files

Install

Open Claude Code, paste:

/plugin marketplace add adelaidasofia/investor-relations-mcp/plugin install investor-relations-mcp@investor-relations-mcp

Then fill in pitch_config.yaml with your company's pitch positioning and global objections (drives the investor_prep tool), set INVESTOR_MCP_VAULT_CRM to your CRM folder, restart Claude Code, and run:

"Run investor_sync" "Show me my investor pipeline" "Prep me for my meeting with [name]"

Legacy install
bash
pip install fastmcp pyyaml python-frontmatter
  1. Clone:

    bash
    git clone https://github.com/adelaidasofia/investor-relations-mcp.gitcd investor-relations-mcp
  2. Fill in pitch_config.yaml with your company's pitch positioning and global objections. This is what drives the investor_prep tool.

  3. Set environment variables:

    bash
    export INVESTOR_MCP_VAULT_CRM="~/vault/CRM/"
  4. Register with Claude Code:

    bash
    claude mcp add investor-relations -s user -- python3 /path/to/investor-relations-mcp/server.py
  5. Restart Claude Code, then sync your CRM:

    "Run investor_sync" "Show me my investor pipeline" "Prep me for my meeting with [name]"

CRM file format

The server reads Obsidian markdown files where relationship: investor in the frontmatter:

markdown
---relationship: investorcompany: Acme Venturesrole: Partneremail: [email protected]location: New Yorkpriority: highnext_step: Follow up after pitch deck revision---
Bio paragraph goes here.
## Timeline- 2026-03-15 — Met at TechCrunch NYC event- 2026-03-22 — Sent intro email with one-pager- 2026-04-01 — Zoom call, strong interest in the model

pitch_config.yaml

This file configures your pitch positioning and global objection rebuttals:

yaml
company_name: "Your Company"raise_amount: "$500K"raise_description: "seed round"
pitch_positioning:  market: "Your market description..."  model: "How you make money..."  traction: "Your best proof point..."  ask: "Use of funds + runway..."  never_say: "Framings to avoid..."
global_objections:  - - "The market is too small"    - "Your rebuttal..."

Environment variables

VariableDefaultDescription
INVESTOR_MCP_DB./investors.dbSQLite database path
INVESTOR_MCP_VAULT_CRM~/vault/CRM/Folder with investor CRM files

Pipeline stages

not_contacted → outreach_sent → response_received → meeting_scheduled → pitched → decision_pending → committed / passed

Stages can be customized in pitch_config.yaml.

Related MCPs

Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):

Telemetry

This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.

What is sent:

  • Plugin name (e.g. slack-mcp)
  • Plugin version (e.g. 0.1.0)

What is NOT sent:

  • No user identifiers, names, emails, tokens, or API keys
  • No file paths, message content, or anything from your work
  • No IP address is stored after dedup processing

Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.

Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.

License

MIT


Built by Mycelium AI.

Source: README.md at commit 40c4b68

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

Other Meeting integrations