---
title: "Server endpoints"
url: "https://www.sensomcp.com/en/doc/mcp-connection/endpoints"
lang: "en-GB"
description: "The endpoints exposed by the Senso MCP server: understanding them to configure a client and troubleshoot a connection."
category: "MCP Server & AI Integration"
author: "Fred Oliver"
published: "2026-09-07T14:58:02+00:00"
modified: "2026-09-28T07:33:05+00:00"
---

# Server endpoints

- Abstract: This page lists the MCP server endpoints: the main URL in the form https://your-site.tld/api/index.php/v1/mcp exposed by the Joomla API, the two OAuth discovery documents served under .well-known, and the JSON-RPC HTTP transport used to list and call tools.
- URLs exposed by the MCP server and OAuth discovery.
- Intermediate
- mcp-server-url, MCP server URL
- oauth-discovery-well-known, OAuth discovery (.well-known)
- transport-format, Transport & format

## MCP server URL

The main endpoint takes the form `https://your-site.tld/api/index.php/v1/mcp`. This is the address you need to provide to your AI client. It is published through Joomla's web services API; your site's exact URL is shown in the component's **Settings**.

[![endpoint](https://www.sensomcp.com/media/yootheme/cache/4c/endpoint-4cf190c9.jpg?src=images/screenshots/endpoint.jpg&thumbnail=800,139,&hash=c4258598)](https://www.sensomcp.com/images/screenshots/endpoint.jpg)

## OAuth discovery (.well-known)

Two discovery documents are served at the domain root:

- `/.well-known/oauth-protected-resource`
- `/.well-known/oauth-authorization-server`

They automatically tell the client how to authenticate (authorization endpoints and supported methods). The client reads them automatically, so no manual OAuth configuration is required.

## Transport & format

Communication takes place over **HTTP** using the MCP protocol format (JSON-RPC). The server responds to client requests: tool listings, tool calls, and results.