About Tend
Tend's MCP connector gives assistants read-only access to a user's goals, contacts, commitments, reminders, and interaction history. It is for people who want answers grounded in their relationship network, without allowing the assistant to alter records.
Key features
- 01Read-only access to Tend records
- 02Goal and commitment queries
- 03Ranked contact search
- 04Interaction history and reminders
- 05Deep links to Tend records
Use cases
- 01Review commitments due this week
- 02Find contacts relevant to a job specification
- 03Prepare a briefing before a conversation
- 04Identify a stalled goal and next moves
MCP support
The hosted MCP server at https://www.tendladder.com/api/mcp uses streamable HTTP and OAuth 2.1. It exposes seven read-only tools for goals, contacts, commitments, activities, and reminders.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://www.tendladder.com/api/mcpclaude mcp add --transport http com-tendladder-tend https://www.tendladder.com/api/mcp{"mcpServers":{"com-tendladder-tend":{"type":"http","url":"https://www.tendladder.com/api/mcp"}}}Open in Cursor{"servers":{"com-tendladder-tend":{"type":"http","url":"https://www.tendladder.com/api/mcp"}}}Open in VS Code{"mcpServers":{"com-tendladder-tend":{"type":"http","url":"https://www.tendladder.com/api/mcp"}}}{"mcpServers":{"com-tendladder-tend":{"serverUrl":"https://www.tendladder.com/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMETend — 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:
| Ask | What 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.
| Tool | Returns |
|---|---|
list_goals | Your goals and their state |
get_goal_next_moves | The next moves on a goal, with the audit's own reasoning and its age |
list_commitments | Open commitments, each carrying a direction — mine or theirs |
search_contacts | Contacts matching a query, ranked |
get_contact | One person in full |
search_activities | Interaction history |
list_reminders | What 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.