Sphere

io.getspherePublished by getsphere.ioOfficial publisherv1.4.0Updated Oct 24, 2026

Log meals, check calories and macros, set up a nutrition plan, and search foods.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Sphere is a remote MCP server that lets an assistant log meals, check calories and macros, set up a nutrition plan, and search foods.

What you can do
Log meals and record what was eaten, so an assistant can keep a running food diary for you. Check calories and macronutrient totals against your day or plan. Set up a nutrition plan and use it as the target for tracking. Search a food database to find items and their nutrition values before logging them.
When to use it
Useful when you want an assistant to help with everyday nutrition tracking: recording meals as you eat them, reviewing calorie and macro intake, or building and following a nutrition plan.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's API host. Authentication is OAuth and is required, so you need a Sphere account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your Sphere account, so review the scopes you grant. Logging meals and setting up a nutrition plan write data to your account. Nutrition figures come from the service's food database and are not medical advice.

Installation

In SourceWeft

  1. Open Sphere 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/io.getsphere%2Fsphere/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": {
    "sphere": {
      "type": "http",
      "url": "https://api.getsphere.io/functions/v1/mcp"
    }
  }
}

README

This repository has no README.

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.4.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.