Tempi account

com.meettempiPublished by meettempi.comOfficial publisherv1.0.0Updated Oct 24, 2026

Run your own Tempi scheduling account: event types, working hours, calendars and bookings.

The publisher's own server: Tempi

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant manage a Tempi scheduling account: event types, working hours, calendars and bookings.

What you can do
This remote MCP server connects an assistant to a Tempi scheduling account. According to the registry description, it covers event types, working hours, calendars and bookings, so an assistant can work with the scheduling setup and the appointments recorded there. No individual tools are listed in the supplied material.
When to use it
Worth adding when you use Tempi for scheduling and want an assistant to handle event types, availability and bookings without switching to the web interface. Less useful if you do not keep your calendar or booking data in Tempi.
Requirements
A remote endpoint at over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no packages, so nothing else is stated as required.
Before you install
The manifest declares no authentication, so it is unclear how access to your scheduling account is controlled or who can reach the endpoint. Scheduling data such as calendars, working hours and bookings is personal and may be read or changed by the assistant; confirm how the connection is authorized before installing.

Installation

In SourceWeft

  1. Open Tempi account 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.meettempi%2Ftempi-account/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": {
    "tempi-account": {
      "type": "http",
      "url": "https://meettempi.com/mcp/account"
    }
  }
}

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

1
  1. v1.0.0LatestSep 26, 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.

Other Meettempi integrations