Tend

com.tendladderPublished by tendladder.comOfficial publisherv1.0.1Updated Oct 24, 2026

Your own network — goals, commitments and interaction history — read-only, from your assistant.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Tend is a hosted, read-only MCP connector that lets an assistant answer questions from your own Tend record of goals, contacts, commitments and interaction logs

What you can do
Read goals and the next moves on each goal, with the reasoning behind them and its age. List open commitments, marked as yours or theirs, and list scheduled reminders. Search contacts by query and open one person's full profile. Search interaction history. Return deep links back into Tend so answers stay traceable.
When to use it
Useful when you want your assistant to answer questions about your own network mid-conversation: what you owe people, what you are waiting on, who to contact and why, which goal is stalling, a briefing on one person, or matching a pasted job spec against your contacts.
Requirements
A remote streamable HTTP endpoint at the provider's site; nothing to install locally. Requires a Tend account (the free plan includes the connector) and OAuth 2.1 sign-in with consent on the provider's domain. Verified on Claude desktop, web and mobile; other clients are expected to work but untested.
Before you install
The connector is read-only: no tool creates, edits, sends or deletes, so a confused agent can only give a wrong answer, not change your record. It reads your personal relationship and commitment data, which is sent to your assistant's provider; the README states it is single-tenant, encrypted, never sold and not used for model training. Connected clients can be revoked individually in Tend settings.

Installation

In SourceWeft

  1. Open Tend in the dashboard and add it to a workspace.
  2. 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.tendladder%2Ftend/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.

{
  "mcpServers": {
    "tend": {
      "type": "http",
      "url": "https://www.tendladder.com/api/mcp"
    }
  }
}

README

Tend — MCP connector

Read-only access to your own Tend record — goals, contacts, commitments and interaction history — so your assistant can answer from your network instead of guessing.

https://www.tendladder.com/api/mcp

Streamable HTTP · OAuth 2.1 · read-only · requires a Tend account (the free plan includes the connector).

This repository is the connector's documentation and its registry manifest. The server itself is hosted — there is nothing here to install or run.

What it is for

Tend is goal-coupled relationship management: your network organized around what you are trying to achieve, rather than a contact list on a reminder timer.

The connector exists because the useful question is usually asked somewhere Tend has no app — in the middle of a conversation with your assistant, on a phone, in a thread about a job you are trying to fill. It answers from your own record, and it never spends your Tend allowance: the reasoning runs on your assistant's plan, not ours.

Connecting

One click: Add Tend to Claude — this opens Claude's Add connector dialog with the name and URL already filled in. Review them, confirm, then click Allow on the consent screen, which appears on tendladder.com rather than a third-party login. That is the whole setup: no token to paste, no config file to edit.

The link only prefills the form. It grants nothing until you confirm.

By hand, if you would rather: in Claude, Settings → Connectors → Add custom connector, and paste https://www.tendladder.com/api/mcp.

Claude Code: claude mcp add --transport http tend https://www.tendladder.com/api/mcp

Verified on Claude desktop, web and mobile. Other MCP clients speak the same protocol and are expected to work, but only Claude is tested — ChatGPT requires Developer mode, and Gemini currently has no consumer path for remote MCP servers.

Every connected client is listed in Tend's settings with its own Revoke.

What to ask

The connector tells your assistant the questions it answers best, so asking "what can I do with Tend?" returns a useful list on the first try. These are the six it names:

AskWhat it does
What do I owe people this week?Your open commitments, the ones you promised
What am I waiting on?The other direction — what others owe you
Who should I contact today, and why that person?Ranked, with the reason attached
Which of my goals is stalling?The goal that has stopped moving, and why
Brief me on Dana before I speak to her.Everything on one person, in reading order
Here is a job spec — who in my network is relevant?Paste anything; it matches against your network

That last one is the one Tend's own app cannot do, because it cannot see what is in front of you and your assistant can.

Tools

Seven, all read-only.

ToolReturns
list_goalsYour goals and their state
get_goal_next_movesThe next moves on a goal, with the audit's own reasoning and its age
list_commitmentsOpen commitments, each carrying a direction — mine or theirs
search_contactsContacts matching a query, ranked
get_contactOne person in full
search_activitiesInteraction history
list_remindersWhat is scheduled

Rows carry deep links back into Tend, so anything your assistant creates elsewhere stays traceable to why it mattered.

Read-only is a hard boundary, not a first version's limitation. No tool creates, edits, sends or deletes. The worst outcome of a confused agent is a wrong answer, never a changed record — which is the property that made shipping this early defensible in the first place.

Privacy

  • Your data is single-tenant and encrypted. It is never sold and never used to train models.
  • Tenancy is resolved from your OAuth session, never from anything the model says — the server cannot be talked into reading someone else's record.
  • Full policy: https://www.tendladder.com/privacy

Registry

Published to the Official MCP Registry as com.tendladder/tend. The manifest is server.json.

Support

Questions, or something behaving oddly: open an issue here, or use the contact route at https://www.tendladder.com/.

License

The documentation and manifest in this repository are MIT licensed (see LICENSE). The Tend service itself is proprietary and is not distributed here.

Source: README.md at commit 7201c40

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts