Skip to main content
SimpleFunctions is CLI-first and API-second. Use MCP only when the agent already runs inside an MCP-compatible client and should call SimpleFunctions tools through that adapter.

​
Claude Code

claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp
Then ask Claude Code to call SimpleFunctions tools for market search, world state, screen, inspect, query-gov, or query-econ.

​
Remote transport

GET /api/mcp/{transport}
POST /api/mcp/{transport}
The transport exposes SimpleFunctions tools over MCP. Public tools work without user credentials. Account, portfolio, intent, and exchange-sensitive tools require auth.

​
What agents can call

JobTool family
Search marketsquery, scan, screen, new markets.
Read world stateworld snapshot, world delta, inspect.
Pull source contextgovernment, economic, traditional-market anchors.
Evaluate thesesthesis context, signals, evaluations.
Read account stateauthenticated theses, intents, portfolio.
Route workflowsintents and runtime tools when authorized.

​
Tool discovery

curl "https://simplefunctions.dev/api/tools"
Local CLI equivalent: 
sf describe --all --json
sf tools search "world delta" --json
Use the CLI manifest when the agent is running on the user’s machine. Use /api/contracts/tools for strict SDK/Agent canonical tools. Use /api/tools when the agent is remote and needs the broad hosted HTTP compatibility inventory. Use MCP last, only when the remote client requires MCP.

​
Suggested first calls

world_state
query("Fed rate cut")
inspect_ticker("KXRATECUT-26DEC31")
query_econ("unemployment rate")
query_gov("SAVE Act")
Start with read-only tools. Require explicit authorization before using write, runtime, or trade tools.