Platform7n

tech.p7nPublished by p7n.techOfficial publisherv0.3.4Updated Nov 7, 2026

Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Connects an assistant to Platform7n workspaces — chat, links, work and decks — through a remote endpoint or a local npm package, with OAuth sign-in.

What you can do
  • No tools are listed in the manifest, so capabilities are known only from the short description.
  • The server is described as connecting an assistant to Platform7n workspaces.
  • The named workspace areas are chat, links, work and decks.
  • Sign-in is described as one-click OAuth.
When to use it
Worth considering if your team keeps chat, links, work items and decks in Platform7n and you want an assistant to work with that content. Because no tool list or documentation is published, verify what it can actually do before relying on it.
Requirements
A Platform7n account with OAuth authorization; the server is offered as a remote endpoint and as a local npm package run over stdio, so a local install needs Node.js. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Platform7n workspace content, so review the scopes requested during sign-in. The tool set is undocumented, so it is unclear whether it can modify, send or delete workspace data.

Installation

In SourceWeft

  1. Open Platform7n 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/tech.p7n%2Fplatform7n/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": {
    "platform7n": {
      "type": "http",
      "url": "https://api.p7n.tech/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

4
  1. v0.3.4LatestNov 7, 2026
  2. v0.3.3Oct 30, 2026
  3. v0.2.2Oct 26, 2026
  4. v0.1.1Sep 16, 2026

Score

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

    Declare a license in the repository or the registry entry.