ADoor

com.halmoslabsPublished by halmoslabs.comv0.1.1Updated Oct 29, 2026

Read and update the tables in your ADoor workspace from an MCP client.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

ADoor connects an MCP client to your ADoor workspace so an assistant can read and update the tables stored there.

What you can do
  • Read the tables in your ADoor workspace
  • Update table records in that workspace
  • Work through an MCP client against a hosted ADoor endpoint
When to use it
Useful if your team keeps structured data in ADoor tables and you want an assistant to look things up or apply changes there without leaving the chat client.
Requirements
A remote MCP endpoint at app.adoor.run, reachable over streamable HTTP. OAuth sign-in to an ADoor account is required; no environment variables or headers are declared.
Before you install
The server can update tables, so assistant actions may change or overwrite workspace data; review write operations before approving them. Access is granted through OAuth to your ADoor account, so scope the authorization to what you need.

Installation

In SourceWeft

  1. Open ADoor 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/com.halmoslabs%2Fadoor/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": {
    "adoor": {
      "type": "http",
      "url": "https://app.adoor.run/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.1.1LatestOct 29, 2026
  2. v0.1.0Oct 21, 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.