Smacros: smarter macro tracking
app.smacrosPublished by smacros.appOfficial publisherv2026.10.28Updated Oct 29, 2026
All the ease of Claude. All the rigor of a real macro tracker.
Overview
Remote MCP endpoint from Smacros that connects an assistant to a macro tracker, combining conversational ease with structured macro tracking.
- What you can do
- The listing gives no tool list, so capabilities are inferred from the short description only.
- It presents itself as a macro tracker that an assistant can use with the ease of a chat assistant.
- It claims the rigor of a real macro tracker, suggesting structured logging of nutrition and macros.
- No specific actions, data fields or reports are documented.
- When to use it
- Consider it if you want an assistant to help log and track daily macros and nutrition through a hosted Smacros account rather than a spreadsheet or manual app entry. Because no tools are documented, verify what it can actually do before relying on it.
- Requirements
- A remote streamable HTTP endpoint at app.smacros.app; no local package or runtime is needed. OAuth authentication is required, so a Smacros account and a client that supports OAuth sign-in are needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Smacros: smarter macro tracking 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/app.smacros%2Fmacro-tracker/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": {
"smacros-smarter-macro-tracking": {
"type": "http",
"url": "https://app.smacros.app/mcp"
}
}
}Tools
0Version history
1- v2026.10.28LatestOct 29, 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.