Changelog

search_issues now accepts an optional milestone filter. Combine it with state and label to narrow a repository search to the work assigned to a particular release, instead of asking your agent to sift through every open issue. Use list_milestones first to discover the exact milestone title. In the acme/sdk example, filtering open bugs by v2.0 returns four matching issues. The response still includes returned_count and truncated, so a short result can be distinguished from a capped one. Existing calls continue to work without a milestone argument. Omit the filter to search across milestones; an unknown title returns no matches. No additional permissions are needed, and the connection remains read-only.

Added list_labels and list_milestones so your agent can inspect a repository’s available filters before constructing a search. This removes the need to guess whether the project uses bug, defect or another label, or which release milestone is currently open. Label results include names and descriptions. Milestone results include titles, descriptions and state. Both tools operate on one explicit repository and support limits from 1 to 50, with a default of 20. Check truncated before treating a returned list as the complete catalog. Use the returned names directly in search_issues. Existing search and single-issue calls are unchanged. After updating the server, refresh your client’s MCP connection and verify that both new tools appear in its tool list.

Added get_issue for reading an individual issue after finding it in search. Supply the repository and issue number to retrieve its title, full description, state, labels and milestone in one focused request. Search results remain compact summaries. Your agent can now use search_issues to identify relevant work, then call get_issue only for the records that need closer inspection. For example, opening #412 in acme/sdk reveals the context behind the issue without requesting the rest of the repository. Comments and attachments are outside this release’s tool contract. The new tool uses the same repository authorization and does not modify issues. Existing search arguments and result limits are unchanged.

The first Toolport release introduces search_issues: a read-only way to bring issue-tracker context into an MCP-compatible client. Start with one authorized repository, then narrow the request with state and label filters instead of loading unrelated project data. Search returns issue summaries with the metadata needed to choose a useful next step. Requests use a default limit of 20 and accept up to 50 results. The returned_count and truncated fields make the size and completeness of each response explicit. This initial release supports searching rather than creating, editing or closing issues. Connect your client, confirm tool discovery and try a narrow query such as finding open bugs in acme/sdk. Repository access stays within the read-only scope of the supplied credentials.