crewlog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREWLOG_KEY | Yes | Team key for the log backend | |
| LINEAR_API_KEY | Yes | Linear API key (lin_api_...) | |
| SLACK_USER_TOKEN | Yes | Slack user token (xoxp-...) | |
| CREWLOG_CONVEX_URL | Yes | Convex deployment URL (https://<deployment>.convex.cloud) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whats_nextA | What the current user should work on next. Call this when the user asks what to do, what's next, what their priorities are, or at the start of a work session. Shows the coordinator's daily briefing (company-wide priorities), then their in-progress issues, their queue by priority, and urgent unassigned work from Linear. |
| team_statusA | Who on the team is working on what right now, from Linear. Call this when the user asks what the team is doing, whether someone is already on a task, or before picking up work that might overlap with a teammate. |
| get_issueA | Full detail for one Linear issue by identifier (e.g. REF-123): description, state, assignee, priority, and all comments. Call this before starting work on an issue or when the user references an issue id. |
| search_linearA | Search Linear issues by text. Call this to find issues about a topic, feature, or bug when you don't have an identifier. |
| update_issueA | Update a Linear issue's state, assignee, and/or priority. Call this when the user starts work (state → In Progress), finishes (state → Done/In Review), or asks to reassign or reprioritize. State is matched by name against the issue's team workflow. |
| comment_on_issueA | Add a markdown comment to a Linear issue. Call this to record findings, decisions, or progress on an issue so the team sees it. |
| create_issueA | Create a new Linear issue. Call this when work is discovered that isn't tracked yet — a bug found while coding, a follow-up task, or something the user asks to capture. |
| search_slackA | Search Slack messages with your visibility. Supports Slack query syntax: "in:#channel", "from:@name", quoted phrases. Call this to find past discussion, decisions, or context about a topic. |
| slack_channel_historyA | Recent messages from one Slack channel, oldest first. Call this to catch up on a channel (e.g. #eng, #standup) or check the latest discussion before starting work. |
| activity_logA | The company-wide activity feed: Slack messages, Linear changes, call summaries, and teammates' agent work logs merged into one timeline. Call this when the user asks "what happened", "what did I miss", "what has the team been doing", or to catch up after time away. When both source and actor are set, fewer than limit rows may come back. |
| search_logA | Full-text search over the company activity log — the one place that also contains teammates' agent work summaries. Call this to find who touched a topic, past decisions, or work that never made it into an issue. |
| log_workA | Append a short work summary to the shared company activity log so every teammate's agent can see it. Call this after completing significant work, making a decision, or starting a task others should know about. Keep it to 1-3 sentences. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct purpose: Linear issue operations, Slack queries, activity log actions, and coordination tools. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_issue, search_slack, log_work). Minor abbreviation in 'whats_next' is acceptable.
12 tools is well within the ideal range and covers all necessary actions for team coordination without being excessive.
The tool set covers core workflows: issue lifecycle, Slack context, activity logging, and status queries. Minor omissions like issue deletion or Slack messaging are acceptable given the domain scope.