General Tools

letsbuddyup.com

Manages user accounts and profiles for the BuddyUp social app.

1 endpoint15 known toolsFirst detected June 15, 2026Last detected August 25, 2026

ENDPOINT 1

https://letsbuddyup.com/api/mcp

No auth detected

MCP server metadata

Name: buddyup-mcp
Version: 1.0.0

Capabilities

toolsresourceslogging

Server instructions

BuddyUp lets AI agents sign users up and interact on their behalf. Call tools/list to discover tools. For a fresh user, start with signup_user (no auth needed) — the response includes a bearer token + one-tap mobile sign-in URL. For everything else, pass the bearer token via Authorization header OR as the `token` argument.

Known tools 15

signup_user

Create a new BuddyUp account and return a bearer token plus a one-tap mobile sign-in URL.

Potential side effects

get_me

Fetch the currently authenticated user's profile.

Inferred read-only

update_profile

Update the authenticated user's profile.

Potential side effects

upload_photo

Upload a profile photo.

Potential side effects

get_user_profile

Fetch a public BuddyUp user profile by slug (the trailing component of letsbuddyup.com/profile/{slug}).

Inferred read-only

send_buddy_request

Send a buddy request to another user by slug.

Potential side effects

accept_buddy_request

Accept a pending buddy invitation (as invited by another user).

Inferred read-only

decline_buddy_request

Decline a pending buddy invitation.

Inferred read-only

check_inbox

Primary polling endpoint.

Inferred read-only

list_chats

List active chats with unread counts and last-message preview.

Potential side effects

get_messages

Fetch messages for a chat.

Inferred read-only

send_message

Send a message in an existing chat.

Potential side effects

list_activities

List canonical BuddyUp activity ids.

Inferred read-only

list_events

Query the public aggregated local-events feed (same backend as letsbuddyup.com/events2).

Inferred read-only

build_signup_fallback_url

Build a pre-filled https://letsbuddyup.com/signup-with-ai?...

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.buddyup-mcp]
url = "https://letsbuddyup.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "buddyup-mcp": {
      "type": "http",
      "url": "https://letsbuddyup.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: buddyup-mcp
Remote MCP URL: https://letsbuddyup.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "buddyup-mcp": {
      "url": "https://letsbuddyup.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "buddyup-mcp": {
      "type": "http",
      "url": "https://letsbuddyup.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "buddyup-mcp",
  "transport": "streamable-http",
  "url": "https://letsbuddyup.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.