- Home
- MCP servers
- Togello
Togello
- javascript
0
GitHub Stars
javascript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"toru-takagi-togello-mcp-server": {
"command": "npx",
"args": [
"-y",
"togello-mcp-server"
],
"env": {
"TOGELLO_API_TOKEN": "replace_with_your_token"
}
}
}
}The Togello MCP Server implements the Model Context Protocol (MCP) to manage context in applications. It exposes a set of context-related resources and tasks, enabling you to fetch categories, activities, and calendar data, and to create, update, and log tasks and activities in a consistent, pluggable way.
How to use
You integrate an MCP client with this server to access resources and perform actions such as listing categories and activities, managing tasks, and tracking activity logs. Use the available commands or endpoints described by your MCP client to fetch data, create or update tasks, and control activity logging. When you start interacting, you can rely on the provided tool definitions to understand what each action returns and how to chain operations (for example, listing categories, then selecting a category to filter tasks, or starting and completing activity logs in sequence). Remember to supply any required authentication tokens through your environment configuration.
How to install
Prerequisites you need installed on your machine: Node.js (with npm) or a compatible runtime for running MCP servers, and network access to reach the MCP endpoints. You will also configure an authentication token to authorize your client with the Togello MCP server.
Install and run the server using the configured command and environment variables shown in the example configuration. The server runs as a local process and is designed to be invoked by MCP clients rather than opened in a browser.
Configuration and usage notes
The server is configured via a JSON snippet that defines how to start the MCP server process and passes in required environment variables. You will typically store this configuration in your MCP environment or tooling to ensure the server starts with the correct authentication token.
{
"mcpServers": {
"togello": {
"command": "npx",
"args": ["-y", "togello-mcp-server"],
"env": {
"TOGELLO_API_TOKEN": "replace_with_your_token"
}
}
}
}
Available resources and endpoints
Resources provide structured data you can query from the MCP server. These include the category list and the activity item list, which help you understand the available classifications and actions.
Tools and actions allow you to manage tasks and track work within the context framework. The server supports a range of operations for tasks, categories, calendars, and activity logs.
Security and tokens
Authenticate to the Togello MCP server by supplying a valid API token via the environment variable shown in your configuration. Treat this token as sensitive credentials and rotate it as needed.
Available tools
category-list
Fetches the list of task categories. Provides category names and UUIDs via the URI toggello://category-list.
activity-item-list
Fetches the list of activity items. Provides item UUIDs and names via the URI toggello://activity-item-list.
get-tasks-list
Retrieves unfinished tasks. Returns task UUID, name, scheduledStartDate, scheduledEndDate, priority, and category.
create-task
Creates a new task. Requires taskName and may include categoryUUID, scheduledStartDate, and url as optional parameters.
update-task
Updates a task’s status. Requires the task UUID obtained from get-tasks-list.
get-todo-category-list
Fetches the list of TODO categories, including category name and UUID.
get-today-calendar
Retrieves yesterday, today, and tomorrow’s events from the integrated Google Calendar, with event name and start/end times.
get-activity-item-list
Fetches activity items, returning item UUID and item name.
get-activity-log-list
Fetches activity logs. End times being null indicate an ongoing activity; non-null end times indicate completed logs.
start-activity-log
Starts an activity log by providing the activity item name obtained from get-activity-item-list. Can be called when there is no currently running activity.
complete-activity-log
Completes the currently running activity log using the UUID obtained from get-activity-log-list.
get-japan-current-time
Returns the current time in JST.