Cabinet Project
app.cabinetprojectPublished by cabinetproject.appOfficial publisherv1.0.0Updated Oct 24, 2026
Cabinet quotes, job status, selling prices and kitchen estimates. Read-only tools with OAuth.
Overview
Lets an assistant look up cabinet quotes, job status, selling prices and kitchen estimates through read-only OAuth tools.
- What you can do
- Cabinet Project is a remote MCP server that gives an assistant access to cabinet-related business data. According to the registry description, it covers cabinet quotes, job status, selling prices and kitchen estimates. The tools are described as read-only and authenticated with OAuth. No individual tool names are listed in the manifest.
- When to use it
- Useful when an assistant needs to answer questions about cabinet quotes, current job status, selling prices, or kitchen estimates without opening the provider's own interface. It suits read-only lookups rather than editing or creating records. Skip it if you need to change data or work without an OAuth connection.
- Requirements
- A remote MCP endpoint reached over streamable HTTP at the provider's API host; no local package or runtime is declared. Authentication is OAuth, and no environment variables or headers are declared. Network access to the provider's endpoint is required.
Installation
In SourceWeft
- Open Cabinet Project 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/app.cabinetproject%2Fdealer/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": {
"cabinet-project": {
"type": "http",
"url": "https://api.cabinetproject.app/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 11, 2026
Score
67% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.