Veles CPQ

com.getvelesPublished by getveles.comOfficial publisherv1.2.0Updated Oct 24, 2026

Configure, price, and quote with Veles CPQ

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Veles CPQ server that lets an assistant configure, price and quote products through the vendor's hosted platform.

What you can do
  • Configure products and build configurations for quotes
  • Price configured products and produce quotes
  • Work inside the Veles CPQ platform through an OAuth-connected remote endpoint
  • No tool list is published, so the exact actions available are not documented in the provided material.
When to use it
Consider it when sales or quoting work already runs on Veles CPQ and you want an assistant to help build configurations, prices and quotes without leaving the conversation.
Requirements
A remote MCP endpoint at app.getveles.com over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so a Veles account with access to the CPQ platform is needed. No environment variables or headers are declared.
Before you install
The server is hosted by a third party and requires OAuth sign-in, so the assistant acts with your Veles account permissions. Quoting and pricing work can create or change commercial records; review outputs before sending them to customers. No tool list is published, so verify what it can write before connecting.

Installation

In SourceWeft

  1. Open Veles CPQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.getveles%2Fcpq/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "veles-cpq": {
      "type": "http",
      "url": "https://app.getveles.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestSep 16, 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.