Flowdex

dk.flowdexPublished by flowdex.dkOfficial publisherv0.2.0Updated Oct 24, 2026

Read and write your team's shared, AI-readable wiki from any MCP client.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Flowdex is a remote MCP server that lets an assistant read and write your team's shared, AI-readable wiki from any MCP client.

What you can do
Read content from your team's shared wiki through an MCP client. Write and update wiki content on the team's behalf. Work with the wiki from any compatible MCP client over a remote connection.
When to use it
Useful when your team keeps documentation in a shared Flowdex wiki and you want an assistant to look things up or add and update entries without leaving the chat client.
Requirements
A remote MCP endpoint at mcp.flowdex.dk using streamable HTTP. OAuth authentication is required, so you need a Flowdex account with access to the team's wiki. No environment variables or headers are declared.
Before you install
The server can write to your team's shared wiki, so assistant changes may be visible to teammates and could overwrite or alter existing content. Access is granted through OAuth to your Flowdex account; review what the authorization covers before connecting.

Installation

In SourceWeft

  1. Open Flowdex 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/dk.flowdex%2Fwiki/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": {
    "flowdex": {
      "type": "http",
      "url": "https://mcp.flowdex.dk/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

2
  1. v0.2.0LatestOct 20, 2026
  2. v0.1.0Sep 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 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.