Addness

io.github.AddnessTechPublished by GitHub account AddnessTechv1.0.0Updated Oct 25, 2026

Company brain for teams and AI: read and write goals, to-dos, comments, and knowledge.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Addness is a remote MCP server that gives an assistant read and write access to a team's shared goals, to-dos, comments and knowledge.

What you can do
Read and write team goals and to-dos, so an assistant can review, create or update work items and their statuses. Add and read comments, letting the assistant join discussion around that work. Access shared knowledge, so the assistant can look up and contribute team documentation. Acts as a shared company brain for both people and AI assistants.
When to use it
Useful when a team already keeps its goals, tasks and knowledge in Addness and wants an assistant to work with that content directly, for example to check progress, draft updates or pull in background knowledge.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and is required, so the user must sign in and authorize access to their Addness account.
Before you install
The server can write as well as read: an assistant may create or change goals, to-dos, comments and knowledge in the shared workspace, so changes should be reviewed. Access is granted through OAuth to a team account, so the scope of what the assistant can see and modify should be checked before connecting.

Installation

In SourceWeft

  1. Open Addness 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/io.github.AddnessTech%2Faddness/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": {
    "addness": {
      "type": "http",
      "url": "https://vt.api.addness.com/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 25, 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.