Teak

com.teakvaultPublished by teakvault.comOfficial publisherv1.0.93Updated Nov 6, 2026

Remote MCP server for saving, searching, syncing, and managing Teak cards.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that lets an assistant save, search, sync and manage Teak cards in a Teak vault account.

What you can do
  • Save new cards into the user's Teak collection
  • Search and look up existing cards
  • Sync cards between the assistant's session and the Teak account
  • Manage and organize stored cards
  • No individual tools are documented, so exact actions depend on the server's own tool list.
When to use it
Useful when someone keeps notes, ideas or reference items as Teak cards and wants an assistant to capture and retrieve them without leaving the conversation.
Requirements
A remote MCP endpoint at teakvault.com reached over streamable HTTP; OAuth sign-in to a Teak account is required. No environment variables or headers are declared.
Before you install
The server requires OAuth access to a Teak account, so the assistant can read and change the cards stored there; saving, syncing and managing cards modify account data. Review what the OAuth grant covers before connecting.

Installation

In SourceWeft

  1. Open Teak 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.teakvault%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": {
    "teak": {
      "type": "http",
      "url": "https://teakvault.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

3
  1. v1.0.93LatestNov 6, 2026
  2. v1.0.92Nov 1, 2026
  3. v1.0.91Oct 31, 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.