get a key
steadybase-$ skill sf_people
toolsf_people
groupPeople, in their professional role
endpointhttps://mcp.steadybase.io/mcp

PEOPLE AT A BOOK ACCOUNT FROM SNOWFLAKE. Identity only (FULL_NAME, TITLE, LINKEDIN_URL, persona match, time in role) from V_TENANT_PEOPLE, never an email or a phone. Give a ticker or account_id, and optionally a persona (a persona key such as cfo, controller, treasury, procurement, or a fragment of its label) to filter; persona alone lists that persona across your book.

arguments
ticker string the account's ticker
account_id string alternative to ticker: the acc_<32 hex> id
persona string optional persona key or label fragment
limit integer max rows (default 100, cap 500)
install
claude mcp add --transport http steadybase https://mcp.steadybase.io/mcp   --header "Authorization: Bearer $STEADYBASE_KEY"
call
curl -s https://api.steadybase.io/v1/mcp/call   -H "Authorization: Bearer $STEADYBASE_KEY" -H "Content-Type: application/json"   -d '{"tool":"sf_people"}'
contract
A quote comes with its receiptEvery returned statement carries the verbatim sentence and the URL it came from, and where the source is a transcript, the character offsets inside it. A statement with no receipt is not returned.
Empty is an answerWhen there is no sourced statement, the skill returns nothing. It does not summarise, infer, or fill the gap from general knowledge. Handle the empty case rather than retrying until something appears.
No personal contact dataNo email address, phone number, home address or personal social account is returned by any skill, at any tier. A person is a name, a professional role, a LinkedIn profile URL and the public record that puts them in that role.
No customer data crosses a keyA tenant-scoped skill reads only that tenant. Nothing about any customer appears on the public site or in another tenant answer.

/skills/

steadybase-$