ONES
com.onesPublished by ones.comOfficial publisherv1.0.3Updated Oct 24, 2026
Manage ONES projects, issues, tests, work hours, and Wiki knowledge.
Overview
Hosted ONES MCP server that lets an assistant find and manage projects, issues, sprints, tests, work hours and Wiki pages in an authorized ONES workspace.
- What you can do
- Find and manage projects, issues, sprints and comments
- Work with test cases and work-hour records
- Create and retrieve Wiki knowledge and read supported attachments
- Update issue status and other fields, subject to workspace configuration and account permissions
- When to use it
- Useful when your team tracks work in ONES and you want an assistant to look up projects, summarize issues and comments, search Wiki pages, or draft and update issues without leaving the chat client. Best suited to VS Code with GitHub Copilot or another client that supports remote HTTP MCP servers and OAuth.
- Requirements
- A remote endpoint at the US deployment (us.ones.com/mcp); no local install or repository clone needed. An ONES account with access to a workspace on that deployment, browser-based OAuth authorization, and permission to use MCP servers under your organization's policies. Other regional or private deployments need a different endpoint.
Installation
In SourceWeft
- Open ONES in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.ones%2Fones/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ones": {
"type": "http",
"url": "https://us.ones.com/mcp"
}
}
}README
ONES MCP for GitHub Copilot
Connect GitHub Copilot to ONES to manage projects and work with knowledge in your authorized workspace. This remote MCP server and this repository are maintained by ONES.
Capabilities
- Find and manage projects, issues, sprints, and comments.
- Work with test cases and work-hour records.
- Create and retrieve Wiki knowledge and read supported attachments.
Available tools and actions depend on your account permissions and enabled ONES capabilities.
Requirements
- VS Code with GitHub Copilot and MCP support enabled.
- An ONES account with access to a workspace served by
https://us.ones.com/mcp. - Permission to use MCP servers under your organization's policies.
This endpoint serves the US deployment. Other regional or private deployments may require a different MCP endpoint. Check your workspace's MCP settings before connecting.
Connect in VS Code
- Open the Command Palette and run MCP: Add Server.
- Select HTTP and enter
https://us.ones.com/mcp. - Name the server
ones. For a new workspace connection, choose.mcp.json; for access across projects, choose the global configuration option offered by your client. - Start the server and confirm trust when prompted. Complete the browser-based OAuth authorization: sign in to ONES and review the requested access.
- Open Copilot Chat in an agent mode that supports tools. Use Configure Tools to confirm that the ONES tools are available.
Alternatively, create .mcp.json in your own project's root using the following configuration. If the file already exists, merge the ones entry into its mcpServers object:
Copyable examples: portable-mcp.json uses the .mcp.json format above; vscode-mcp.json uses the servers format for existing .vscode/mcp.json setups. Configure the server in one location to avoid duplicate entries. Cloning this repository or running a local ONES server is not required.
ONES uses OAuth authorization. Do not put passwords, access tokens, or client secrets in configuration files committed to Git. Access remains subject to the authorized ONES user's permissions.
Verify the connection
After saving the configuration, run MCP: List Servers, select ones, and start the server if needed. Complete the browser authorization with the ONES account you intend to use, then return to VS Code. In Copilot Chat, open Configure Tools and check that ONES tools are available and enabled.
Send this first request:
Use ONES to list the projects I can access. Do not change any data.
A successful check returns actual accessible project results, or an explicit empty result if the account has no accessible projects. A generic answer about ONES does not verify a tool call: expand Copilot's tool activity and confirm that an ONES tool ran successfully. If authorization or a tool call fails, use the troubleshooting steps below.
Use ONES in Copilot Chat
Choose a chat mode that supports tools and enable the relevant ONES tools. State the project, issue, or Wiki page you want to work with. When names are ambiguous, ask Copilot to show matching records before proceeding. Replace angle-bracket placeholders below with your own values.
Find and summarize work
Use ONES to find the project named
<project name>. If multiple projects match, let me choose. Then list the issues assigned to me in that project, including their titles and statuses. Do not modify anything.
Use the returned issue identifiers for follow-up requests:
Retrieve ONES issue
<issue ID>and summarize its description, status, and comments.
Retrieve workspace knowledge
Search my authorized ONES Wiki content for
<release process>. Show the matching page titles, retrieve the relevant page, and summarize the release steps. Include the source page link if one is returned.
Results depend on the Wiki content the authorized account can access.
Create an issue
In ONES project
<project name>, prepare an issue titled<title>with this description:<description>. Ask me for any required fields that are missing, and show the target project, issue type, and proposed fields before creating it.
Review the proposed values, then ask Copilot to create the issue. If VS Code requests tool approval, review the operation before approving it. Check the returned issue identifier and open the issue in ONES to verify the saved result. Use a test project when evaluating write operations.
Update an existing issue
Retrieve ONES issue
<issue ID>. Show its current status and the available target statuses, then ask me which status to use before updating it.
Check the resulting record in ONES after the update. Available operations and required fields vary with workspace configuration and account permissions.
Disconnect
Use MCP: List Servers to stop the ones server. To remove the connection configuration, delete only its entry from the configuration file you selected. Stopping or removing the client configuration does not itself revoke an existing OAuth grant; manage that authorization separately in your ONES account settings.
Troubleshooting
- Authorization fails: confirm that your ONES account and workspace belong to the configured deployment, then reconnect and complete OAuth again.
- No tools appear: check the server status with MCP: List Servers, review its output, and check the tool selection in Copilot Chat.
- An operation is denied: confirm your ONES permissions and the workspace's enabled capabilities with an administrator.
- MCP is restricted: ask your organization's administrator whether this server is allowed.
For reproducible integration problems, open an issue with the client version and a sanitized error message. Never include tokens, credentials, or private workspace data.
Registry metadata
The server's Official MCP Registry identifier is com.ones/ones. server.json contains the metadata prepared for publication, including this public repository URL. A file in this repository is not evidence that the corresponding version has been published or approved by GitHub; check the live Registry record for the published version.
This repository provides public documentation and connection metadata for the hosted ONES MCP service. It does not contain the hosted service's backend source code.
Links
Source: README.md at commit 3e74baf
Tools
0Version history
3- v1.0.3LatestOct 8, 2026
- v1.0.2Sep 23, 2026
- v1.0.1Sep 22, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
