tama mcp config

Prints the MCP client configuration fragment for Tama's native MCP server.

#Invocation

tama mcp config

The command takes no required input or public options.

#Output and state

Stdout receives a JSON document whose mcpServers.tama.command is the running tama program and whose args are ["mcp"]: the MCP server is the tama mcp subcommand of the same program. When the running program cannot name its own path, the command is the bare name tama. It never writes client configuration.

#Refusals and failures

There are no command-specific policy refusals. The bare-name answer is valid output rather than a missing-server error; actual server discovery occurs when the client starts that command.

#The server it configures

tama mcp reads one JSON-RPC message per line on standard input and answers each request on one line of standard output; a last line that ends without its newline is not read. It answers initialize, ping, tools/list and tools/call, and any other method with -32601 "Method not found". A notification or a response the client sends is not answered. A line that is not JSON is answered with {"jsonrpc":"2.0","id":null,"error":{"code":-32700,"message":"Parse error: <cause>"}}, and a JSON value that is no request (a field the request schema does not have, jsonrpc other than "2.0", an id that is neither a string nor an integer, params or params._meta that is not an object) with code -32600 and the message Invalid Request: <why>, as JSON-RPC 2.0 requires (error object). If standard input cannot be read, or an answer cannot be written to standard output, the server ends with mcp: standard input cannot be read: <cause> or mcp: an answer cannot be written to standard output: <cause> on standard error and exit status 1.

Return to the complete CLI command tree.