FITsociety
io.fitsocietyPublished by fitsociety.ioOfficial publisherv1.0.0Updated Oct 24, 2026
Access approved FITsociety clients, schedules, bookings and coaching data with AI assistants.
Overview
Lets an assistant read approved FITsociety client, schedule, booking and coaching data through a hosted remote endpoint.
- What you can do
- FITsociety is a remote MCP server reached over streamable HTTP at a fixed hosted address. According to its registry description, it gives AI assistants access to approved FITsociety clients, schedules, bookings and coaching data. No individual tools are listed in the supplied manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when an assistant needs to work with FITsociety coaching or scheduling information, for example looking up clients, schedules or bookings during a conversation. It is only relevant if you already use FITsociety and your data is approved for access.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. The manifest declares no authentication, no environment variables and no headers, and no local package or runtime is needed.
Installation
In SourceWeft
- Open FITsociety in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.fitsociety%2Fmcp/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"fitsociety": {
"type": "http",
"url": "https://mcp.fitsociety.io/mcp/v1"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 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.