MCP tools

The Proxium MCP server gives an AI agent the memory of your project and the tools to read and change the project. To connect a client, see Connect an MCP client.

A tool that does not change data only reads. The traffic and failover tools call the same routes as the console, as you. An agent sees only the projects that you are a member of.

Tool	What it does	Changes data
proxium_list_projects	Lists your projects, their slugs, and the spend and calls of each project in the last 7 days	No
proxium_recall_memory	Reads the knowledge page, the most trusted memories and the newest conversation summaries	No
proxium_search_memory	Searches the memories and the past conversations by words	No
proxium_read_conversation	Reads one past conversation	No
proxium_query_graph	Reads the facts of the knowledge graph about one name	No
proxium_save_memory	Saves one memory: a fact, a preference, a decision, an event or a procedure	Yes
proxium_remember_conversation	Asks Proxium to read one past conversation and write its memories, with an optional focus	Yes
proxium_correct_memory	Replaces the text of a memory	Yes
proxium_rate_memory	Marks a memory useful or wrong	Yes
proxium_forget_memory	Removes a memory	Yes
proxium_resume_memory	Reads where the last sessions stopped: the newest conversations, the newest decisions with their reasons and the newest diary entries	No
proxium_record_decision	Saves a decision and the reason for it as one memory of kind decision	Yes
proxium_write_diary	Writes one entry in the diary of an agent	Yes
proxium_read_diary	Reads the newest diary entries of one agent or of every agent	No
proxium_set_value	Stores one value under a key in a namespace, and replaces the value of an existing key	Yes
proxium_get_value	Reads the value of a key, or lists the newest values of a namespace	No
proxium_add_relation	Writes one relation of the knowledge graph as a memory of kind fact	Yes
proxium_read_spend	Reads the spend of today, 7d or 30d of one project, several or all, split by model, key, app and project. The numbers of Overview	No
proxium_list_failures	Lists the failed attempts of a window in one project, several or all: each reason with its vendor, and each model that failed. What failed and Models and vendors of Requests	No
proxium_list_models	Lists the models of one request type with their prices, and the chain of each tier. The data of Routing	No
proxium_list_recommendations	Lists the findings of Improve in one project, several or all, with the dollars a month that each one can save	No
proxium_read_failover_policy	Reads how the project handles a failed call, and the models and vendors retired now. When a call fails of Routing	No
proxium_set_failover_policy	Changes the failover policy. Only the fields given change. Save of When a call fails	Yes
proxium_retire_model	Retires one model of the project, for some minutes or until it is brought back. The calls skip it, and the tiers stay the same. Retire of Models and vendors	Yes
proxium_restore_model	Brings back a retired model at once. Bring back of Models and vendors	Yes
proxium_retire_vendor	Retires every model of one vendor of the project, for some minutes or until it is brought back. Retire vendor of Models and vendors	Yes
proxium_restore_vendor	Brings back a retired vendor at once. Bring back vendor of Models and vendors	Yes
proxium_list_vendor_allowances	Lists the allowance of each vendor of the project, what its period used and its reset. Allowances of Requests	No
proxium_set_vendor_allowance	Sets the calls or tokens that a vendor, or one model of it, may serve in each day, week or month. At the allowance the vendor is retired until the reset	Yes
proxium_remove_vendor_allowance	Removes the allowance of a vendor or of one model of it. Remove of Allowances	Yes
proxium_read_cache_settings	Reads the cache of the project: on or off, how long an answer lives, and whether a question in other words can match. The data of Settings › Cache	No
proxium_set_cache_settings	Changes the cache of the project. Only the fields given change	Yes
proxium_read_memory_settings	Reads the memory of the project: on or off, the apps it remembers, how often it learns, and its cost this month. The data of Memory	No
proxium_set_memory_settings	Turns memory on or off, chooses the apps it remembers, or sets how often it learns. Only the fields given change	Yes
proxium_list_classifier_profiles	List every classification document of the project: the project's own, and one for each app or key that has its own, with its version and its questions	No
proxium_test_classifier_profile	Run a classification document on a text, as the classifier runs it on a call for auto of the project, an app or a key: one call to the project's classifier chain. It returns the call that was sent, each answer, and what the rules decided	No
proxium_read_systemone_settings	Read whether the project keeps the request and the answer of its /v1/systemone calls	No
proxium_set_systemone_settings	Keep, or stop keeping, the request and the answer of the project's /v1/systemone calls	Yes
proxium_read_classifier_profile	Read the classification document of the project, or of one app or key: what the classifier reads, the questions it asks in one call, and the rules that turn the answers into actions	No
proxium_set_classifier_profile	Save the classification document of the project, or of one app or key, as its next version	Yes
proxium_remove_classifier_profile	Remove the classification document of the project, or of one app or key, as a new version	Yes
proxium_read_classifier_profile_versions	Read every saved version of the classification document of the project, or of one app or key, the newest first: the document, who saved it and when	No
proxium_read_classifier_catalog	Read what a classification document can hold (the question types, the $from parts, the condition fields and operators, the actions, the limits) and the ready-made documents	No
proxium_list_requests	Read the requests of a time window, in one project, several or all of yours. A summary first: the requests, the failed ones, the cost, each caller and the causes of the failed attempts in words. Then 25 requests a page, each with its caller, kind, attempts with the reason of a failure, tokens and cost. Filters: caller, result, kind, page	No
proxium_read_request_trace	Read the trace of one request: each step the gateway took (guard, classifier, cache, each attempt with its vendor, model, status and time) and why it chose each model	No
proxium_read_request_bodies	Read the stored prompt and answer of one request, when the project captures them (proxium_read_capture_settings)	No
proxium_read_cache_report	Read what the response cache served in a time window, in one project, several or all of yours: hits, misses, saved cost and the top cached calls	No
proxium_read_waste	Read the cost of the answers that a call moved past, in one project, several or all of yours: an empty or a cut answer that the vendor billed, with its tokens and cost for each model and app	No
proxium_read_context_size	Read how large the context of the calls is, in one project, several or all of yours: for each app the median, the 90th and the 99th percentile and the largest context in tokens, and the calls in each size bin	No
proxium_read_plan_reuse	Read plan reuse of the project: the mode of each app, and for each tool and guard pair the shadow precision, the gate, the skips, the regrets, and the tokens, model wait and money saved net of the plan blocks	No
proxium_set_plan_reuse	Set plan reuse for one app or for every app: off, shadow or skip, and the thresholds of the gates	Yes
proxium_reset_plan_gates	Close the gates of plan reuse of one app, or of one tool and guard pair, and start their shadow again	Yes
proxium_read_routing	Read the routing of the project: each tier with its chain of models for each request type, who set it (the project or the gateway default), the rules of each app and key, and the classifier chain with its switch and whether auto is classified	No
proxium_set_routing	Set the chain of models of one tier for the project, or for one app or key: the first hop answers, and each next hop takes over on a failure	Yes
proxium_reset_routing	Remove the project's own chain of one tier, or the rule of one app or key, so the next rule applies: the project's, then the gateway default	Yes
proxium_read_routing_document	Read the routing document of the project, or of one app or key: each tier with its chain of models, the reasoning level of each hop, the template and the classifier document, with its version	No
proxium_plan_routing_document	Check a routing document and show what applying it changes, and save nothing: each fault with its path, and each chain that moves	No
proxium_apply_routing_document	Apply a routing document as the next version of the project, an app or a key, when the version it was made from is still in force	Yes
proxium_list_routing_document_versions	List the saved versions of the routing document of the project, an app or a key, the newest first	No
proxium_rollback_routing_document	Apply an earlier version of the routing document of the project, an app or a key again, as the next version	Yes
proxium_read_resolved_routing	Read where a call of the project goes, for one app or one key: each tier with the chain in force, the reasoning level of each hop, and the scope it comes from	No
proxium_list_tiers	List the tiers that the project can route and that a key can carry, with their descriptions	No
proxium_list_routing_presets	List the ready-made routing presets: the tiers and models of each, whether the project has a vendor it routes to, the preset the project uses, and whether auto is classified	No
proxium_use_routing_preset	Use a routing preset for the project, take a copy of the preset in use so a newer version does not change it, or reset to no preset	Yes
proxium_list_vendor_presets	List the known vendors that a project can add with proxium_add_vendor by preset id alone: name, address, models and type of each	No
proxium_read_classifier_report	Read what the classifier did for calls to auto in a time window, in one project, several or all of yours: its calls and failures, who decided (classifier, rule, reuse, fallback), the decisions reused for a task, the tiers, the confidence, and the recent decisions	No
proxium_read_classifier_savings	Read what the classifier saved in the last days: for each tier it chose, the calls, their cost, what the same tokens cost on the baseline tier, and the decisions at each confidence level	No
proxium_read_data_protection	Read the data protection of the project: for each class of sensitive data (keys, emails, cards and others), its action (off, flag, redact or block) and alert, and the custom terms	No
proxium_set_data_protection	Change the action and the alert of classes of sensitive data, or the custom terms	Yes
proxium_reset_data_protection	Remove the project's data protection settings, so the defaults of the gateway apply to every class again	Yes
proxium_list_data_protection_events	Read the matches of the data protection in a time window, in one project, several or all of yours: the class, the action taken, the app and the request id	No
proxium_test_data_protection	Run the project's data protection on a text and return each match and the text as a vendor would receive it	No
proxium_read_capture_settings	Read whether the project stores the prompt and the answer of its calls (all, errors only, or off) and for how many days	No
proxium_set_capture_settings	Change which prompts and answers the project stores (all, errors or off) and the days it keeps them	Yes
proxium_list_keys	List the virtual keys of the project: prefix, label, tier, status, last use, ceilings and MCP tools of each	No
proxium_mint_key	Create a virtual key for the project	Yes
proxium_revoke_key	Revoke a virtual key of the project	Yes
proxium_set_key_limits	Set the ceilings of one key: calls per hour, cost per day in cents, requests and tokens per minute	Yes
proxium_set_key_tools	Set which MCP tools of the project one key may call, and its tool calls per hour	Yes
proxium_list_members	List the members of the project and the open invitations: email, role, status and the MCP tools each one may call	No
proxium_invite_member	Invite a person to the project by email as an owner or a member	Yes
proxium_remove_member	Remove a member or an open invitation from the project	Yes
proxium_set_member_tools	Set which MCP tools of the project one member may call through proxium	Yes
proxium_list_provider_keys	List the vendors for which the project uses its own API key, with the last characters of each key	No
proxium_list_available_providers	List the vendors that the project can route to: by its own key, or by the platform pool when the project has it	No
proxium_set_provider_key	Save the project's own API key for one vendor	Yes
proxium_remove_provider_key	Remove the project's own API key for one vendor	Yes
proxium_list_vendors	List the vendors that the project added itself (an OpenAI-compatible address): name, address, models and type of each	No
proxium_add_vendor	Add an OpenAI-compatible vendor to the project: a preset id alone, or a name, address and models	Yes
proxium_remove_vendor	Remove a vendor that the project added	Yes
proxium_list_endpoints	List the endpoints of the project: each is one key with its own routing, for one app or one use	No
proxium_create_endpoint	Create an endpoint: a new key with its own tier and routes	Yes
proxium_set_endpoint_routes	Replace the routes of one endpoint with the list you give	Yes
proxium_delete_endpoint	Delete an endpoint and revoke its key	Yes
proxium_read_alerts	Read the alert settings of the project: on or off, the spend thresholds, the channels (webhook, Slack, Discord, Telegram) and the spend watches	No
proxium_set_alerts	Change the alert settings of the project	Yes
proxium_list_alert_deliveries	Read the alerts that proxium sent in a time window, in one project, several or all of yours: channel, level, status and time	No
proxium_send_test_alert	Send a test alert to every channel of the project, and return the result of each delivery	Yes
proxium_set_spend_watch	Set a spend level that sends an alert when the project, or one app, spends more in a period	Yes
proxium_remove_spend_watch	Remove the spend watch of the project, or of one app, for one period	Yes
proxium_list_app_limits	List the settings of each app of the project: the ceilings (calls per hour and cost per day) and the cut of long tool results	No
proxium_set_app_limit	Set the ceilings and the cut of long tool results of one app. A field that you leave out keeps its value	Yes
proxium_remove_app_limit	Remove the ceilings of one app, so only the key's and the project's apply	Yes
proxium_read_caps	Read the caps of the project: the ceilings that apply to it and how much of each it used	No
proxium_set_caps	Replace every cap of the project with the list you give: a ceiling of calls or cost for each day or month, for the project, one app or one end user	Yes
proxium_reset_failover_policy	Remove the project's own failover policy, so the defaults of the gateway apply again	Yes
proxium_read_billing	Read the plan, the credits and the billing state of the project	No
proxium_read_readiness	Read whether the project can route a call now, and what is missing when it cannot: a key, a vendor, a chain or credits	No
proxium_read_platform_access	Reads what the operator allows one project to use of the platform: the pooled keys, the platform classifier, and the platform Jev of the cache, the security checks, moderation, rerank and classify. Operators only	No
proxium_set_platform_access	Allows or stops one of those for a project. Only the switches given change. Operators only. Platform access in Settings	Yes
proxium_create_project	Create a new proxium project	Yes
proxium_list_exports	List where the project sends a record of each call (a webhook or an OTLP collector), and whether each one includes the bodies	No
proxium_add_export	Send a record of each call of the project to a webhook or an OTLP collector	Yes
proxium_change_export	Turn a call record destination on or off, or change whether it includes the bodies	Yes
proxium_remove_export	Stop sending call records to one destination, and remove it	Yes
proxium_test_export	Send one test record to a destination and return its HTTP status	Yes
proxium_list_mcp_servers	List the MCP servers that the project added to proxium: name, address, transport, auth, state and tools of each	No
proxium_add_mcp_server	Add an MCP server to the project, so its tools are served through proxium as <server>__<tool>, with the credential kept by proxium	Yes
proxium_change_mcp_server	Turn an MCP server of the project on or off, or turn some of its tools off	Yes
proxium_remove_mcp_server	Remove an MCP server and its credential from the project	Yes
proxium_set_mcp_credential	Save the credential that proxium sends to one MCP server of the project	Yes
proxium_remove_mcp_credential	Remove the credential of one MCP server of the project	Yes
proxium_refresh_mcp_server	Ask one MCP server of the project for its tool list again, and return the server with its tools	Yes
proxium_list_mcp_calls	Read the tool calls that went through proxium to the project's MCP servers, the newest first: tool, caller, outcome and time	No
proxium_list_memories	List the memories of the project, the newest first	No
proxium_review_memory	Confirm a memory that waits for review, or pin one so it is always recalled	Yes
proxium_list_conversations	List the conversations that the project's memory stored, the newest first, for all subjects or one	No
proxium_list_memory_pages	List the pages that the project's memory wrote: one summary for each subject and topic	No
proxium_erase_memory_subject	Erase every memory, conversation and page about one subject, such as a user who asked to be forgotten	Yes