Houston

io.github.aibakeryPublished by GitHub account aibakeryv0.1.0Updated Oct 24, 2026

Read, write, and combine connected apps and databases with shared code and per-person permissions.

VerifiedStreamable HTTPWeb executableDatabasesProductivity & Workflow

Overview

AI-generated overview

Houston is a remote MCP server that lets an assistant read, write and combine connected apps and databases, with shared code and per-person permissions.

What you can do
Read data from connected apps and databases the assistant has access to. Write and update records in those connected sources. Combine data across multiple connected apps and databases. Work through shared code with permissions applied per person.
When to use it
Useful when an assistant needs to work across several connected apps and databases in one place, reading and writing records rather than only querying one source. Suited to teams that want shared code and per-person access control over those connections.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required; no environment variables or headers are declared. No local package or runtime is needed.
Before you install
The server can write to connected apps and databases, so changes may be made to real data. Access is governed by per-person permissions, so review who is granted access and to which sources. OAuth credentials are required and should be handled through the normal authorization flow.

Installation

In SourceWeft

  1. Open Houston 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.aibakery%2Fhouston/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": {
    "houston": {
      "type": "http",
      "url": "https://ok-houston.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. v0.1.0LatestOct 16, 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.