Vondet

com.vondetPublished by vondet.comOfficial publisherv1.1.0Updated Oct 24, 2026

A project planning board your AI reads and updates over MCP, so the plan stays one plan.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Vondet is a remote MCP endpoint for a project planning board that an AI assistant can read and update, keeping one shared plan.

What you can do
  • Read the project planning board's plan and current state.
  • Update the board so the plan stays in sync with what the assistant does.
  • Connect either through OAuth sign-in or with a connection key issued on the board's Connect screen.
When to use it
Useful when a team keeps its project plan on a Vondet board and wants the assistant to work from that plan and keep it current, rather than duplicating it in chat.
Requirements
A remote MCP endpoint at vondet.com over streamable HTTP; no local package or runtime. Authentication is required: OAuth sign-in when connecting, or a connection key from the board's Connect screen sent in the Authorization header.
Before you install
The assistant can change the shared board, so edits affect the whole team's plan. The connection key is a secret sent in the Authorization header; treat it like a password and revoke it if exposed. Board content is sent to the assistant's provider.

Installation

In SourceWeft

  1. Open Vondet 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/com.vondet%2Fmcp/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": {
    "vondet": {
      "type": "http",
      "url": "https://vondet.com/api/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. v1.1.0LatestOct 11, 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 listed15 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.