Atrix AI

dev.atrixPublished by atrix.devOfficial publisherv1.0.0Updated Oct 29, 2026

Work, docs, CRM, calendar, chat and hiring for small teams. OAuth 2.1 with scoped, audited access.

Overview

AI-generated overview

Remote Atrix AI MCP endpoint that gives an assistant OAuth-scoped access to a small team's work, docs, CRM, calendar, chat and hiring data.

What you can do
  • Connect an assistant to an Atrix AI workspace covering work items, documents, CRM records, calendar, chat and hiring.
  • No tool list is published, so the exact actions available are not documented here.
  • Access is granted through OAuth 2.1 with scoped, audited permissions.
When to use it
Useful when a small team already runs its work, docs, CRM, calendar, chat and hiring in Atrix AI and wants an assistant to work with that data instead of switching between apps.
Requirements
A remote MCP endpoint at atrix.dev reached over streamable HTTP; no local package or environment variables are declared. An Atrix AI account and OAuth 2.1 authorization are required.
Before you install
The server reaches business and people data such as CRM records, chat and hiring information, so review the OAuth scopes granted and the audit trail before connecting. No tool list is published, so confirm what the assistant can read or change.

Installation

In SourceWeft

  1. Open Atrix AI 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/dev.atrix%2Fworkspace/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": {
    "atrix-ai": {
      "type": "http",
      "url": "https://atrix.dev/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.0.0LatestOct 29, 2026

Score

83% 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
  • 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.