ArchiCollab

archi.collabPublished by collab.archiOfficial publisherv1.1.0Updated Oct 24, 2026

Interrogez vos projets ArchiCollab : plans, annotations, équipe. Répondez et exportez le PDF. OAuth.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Remote ArchiCollab server that lets an assistant query your projects — plans, annotations and team — and answer and export a PDF, via OAuth.

What you can do
  • Query ArchiCollab projects, including plans and annotations.
  • Look up team information tied to those projects.
  • Answer on the basis of the retrieved project content.
  • Export the result as a PDF.
When to use it
Useful when you work in ArchiCollab and want an assistant to pull project plans, annotations and team details into a conversation, then produce an answer or a PDF export without switching tools.
Requirements
A remote MCP endpoint (streamable HTTP) at the provider's host; no local package or environment variables are declared. OAuth authentication is required, so you need an ArchiCollab account with access to the relevant projects.
Before you install
The server reads project data — plans, annotations and team information — and sends it to the assistant, so check that this is acceptable for your organization. It can export PDFs, which produces files from your project content. Access is granted through OAuth; review which scopes and projects you authorize. No tool list is published, so exact read/write behavior is unverified.

Installation

In SourceWeft

  1. Open ArchiCollab 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/archi.collab%2Farchicollab/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": {
    "archicollab": {
      "type": "http",
      "url": "https://collab.archi/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

2
  1. v1.1.0LatestOct 2, 2026
  2. v1.0.0Sep 30, 2026

Score

67% 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

    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.

Other Collab integrations