Squiredocs

com.squiredocsPublished by squiredocs.comOfficial publisherv1.0.2Updated Oct 25, 2026

Squire Docs — the durable, attributed spec layer for agentic development.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Squire Docs is a remote MCP endpoint that provides a durable, attributed specification layer for agentic development.

What you can do
Provides a durable, attributed spec layer for agentic development, per the registry description. No tool list, instructions or README were supplied, so the specific operations the assistant can perform are not documented here. Access is through a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Consider it when you want an assistant working on agentic development to draw on a persistent, attributed specification layer rather than ad hoc context. Because the available tools are undocumented, confirm its capabilities before relying on it in a workflow.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP, plus OAuth authentication, which the manifest lists as required. No environment variables, headers or packages are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. The tool set and data handling are not documented in the supplied material, so verify what it reads or writes before connecting it to sensitive projects.

Installation

In SourceWeft

  1. Open Squiredocs 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.squiredocs%2Fmcp/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": {
    "squiredocs": {
      "type": "http",
      "url": "https://squiredocs.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.2LatestSep 16, 2026

Score

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

    Publish an icon in the registry entry.

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