# Sequans Website MCP Server

**Canonical:** https://apis.io/apis/sequans/sequans-site-mcp/  
**Provider:** Sequans — https://apis.io/providers/sequans/  
**Base URL:** https://sequans.com/wp-json/mcp/mcp-oauth-server  
**Documentation:** https://sequans.com/

Sequans Website MCP Server is published by [Sequans](https://apis.io/providers/sequans/) on the [APIs.io](https://apis.io/) network. Tagged areas include MCP, Agents, and WordPress. The published artifact set on APIs.io includes authentication docs.

A Model Context Protocol server exposed by the WordPress MCP Adapter running on the sequans.com corporate site. Two MCP endpoints are registered and enumerable anonymously through the WordPress REST route index (/wp-json/mcp): mcp-oauth-server and mcp-adapter-default-server. Both reject anonymous JSON-RPC calls with HTTP 401, so the live tool list is auth-gated, but the OAuth discovery documents (/.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource) are served anonymously and declare an authorization-code + PKCE (S256) flow with a single "mcp" scope. This is the corporate website's agent surface, not an API for Sequans chip or module products.

## Machine-readable artifacts (3)

- **MCPServer** — https://raw.githubusercontent.com/api-evangelist/sequans/refs/heads/main/mcp/sequans-mcp.yml
- **Authentication** — https://raw.githubusercontent.com/api-evangelist/sequans/refs/heads/main/authentication/sequans-authentication.yml
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/sequans/refs/heads/main/apis.yml

## Tags

MCP, Agents, WordPress

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/sequans/sequans-site-mcp/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/sequans/.