Sekichi

io.github.surp-renzPublished by GitHub account surp-renzv0.1.3Updated Nov 7, 2026

Knowledge accumulation for AI coding agents. Records decisions, problems, and insights as context.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Sekichi lets an AI coding agent record decisions, problems, and insights as accumulated context.

What you can do
Sekichi is a remote MCP server aimed at knowledge accumulation for AI coding agents. According to its description, it records decisions, problems, and insights as context, so an assistant can keep that material available across work. No individual tools are listed in the supplied material.
When to use it
Consider it when you want a coding assistant to retain the reasoning behind decisions, recurring problems, and insights rather than losing them between sessions. It suits teams or individuals who want that context stored in one place.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. Authentication is OAuth and is required; no environment variables or headers are declared.
Before you install
The server is hosted by a third party, so recorded decisions, problems, and insights are sent to and stored outside your machine. OAuth grants access to the service; review what it can read or change before connecting. No tool-level write or delete behavior is described in the supplied material.

Installation

In SourceWeft

  1. Open Sekichi 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.surp-renz%2Fsekichi/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": {
    "sekichi": {
      "type": "http",
      "url": "https://sekichi.fly.dev/mcp"
    }
  }
}

README

This repository has no README.

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.3LatestOct 12, 2026
  2. v0.1.2Sep 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.