project_list
List the projects accessible through the workspace connection.
List the projects accessible through the workspace connection. This is a read-only tool requiring projects:read access.
When to use it
After confirming the workspace, to choose a project for subsequent reads.
Arguments
| Argument | Type | Default | Notes |
|---|---|---|---|
limit | integer | 25 | Maximum 100 |
offset | integer | 0 | Non-negative offset |
Response shape
The payload contains projects and page. Projects include IDs, workspace IDs, slugs, names, and timestamps. Follow the returned pagination metadata when more results exist.
Input methods
After your MCP client has authenticated and initialized the connection, send
this tools/call request through that client. This JSON is a request example,
not a standalone authentication or initialization flow.
Use Semogram to list my accessible projects, then ask me which project to inspect.
Use a workspace API key with projects:read. Set SEMOGRAM_API_KEY in your shell; replace resource placeholders with real IDs. This is an HTTP resource request, not an MCP JSON-RPC message.
curl --request GET "https://platform.semogram.com/api/v1/projects" \
--header "Authorization: Bearer ${SEMOGRAM_API_KEY}" \
--get \
--data-urlencode 'limit=25' \
--data-urlencode 'offset=0'This is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "project_list",
"arguments": {"limit":25,"offset":0}
}
}The server wraps operation results in MCP content. Inspect the returned payload and evidence rather than treating the assistant’s summary as the raw response.
FAQ
Does this grant access or change records?
No. The tool uses the existing authenticated account or API-key permissions. It does not grant membership or modify business records.
What if the result is missing or the request fails?
Confirm the workspace URL and account first. See authentication and troubleshooting.