Statey

ai.stateyPublished by statey.aiOfficial publisherv1.0.0Updated Oct 28, 2026

An agent-native database over MCP: shared, validated, structured records in every AI chat.

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & Memory

Overview

AI-generated overview

Statey is a remote, agent-native database over MCP that gives an assistant shared, validated, structured records inside AI chats.

What you can do
  • The manifest lists no individual tools, so capabilities come from the short description only.
  • It presents itself as an agent-native database reachable over MCP, so an assistant can work with structured records rather than free text.
  • Records are described as shared and validated, suggesting data that persists across chats and is checked against a schema.
  • It is intended to be used directly from within AI chat sessions.
When to use it
Worth considering when you want an assistant to keep structured, validated records that stay consistent across multiple AI chats, instead of relying on conversation context alone.
Requirements
A remote MCP endpoint at mcp.statey.ai over streamable HTTP. OAuth authentication is required, so a Statey account and an OAuth sign-in flow are needed. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested during sign-in. The description says records are shared, so assume data written through it may be visible to others with access. No tool list is published, so what it can read, write or delete cannot be verified in advance.

Installation

In SourceWeft

  1. Open Statey 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/ai.statey%2Fstatey/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": {
    "statey": {
      "type": "http",
      "url": "https://mcp.statey.ai/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.0LatestSep 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.