Onepage
API for enriching user and company data, providing endpoints for token validation and generic search.
Verdict
Common use cases
- Surface onboarding docs during new hire chat
- Verify access permissions for shared resources
- Pull policy details into compliance discussions
- Search internal wiki without switching tabs
- Retrieve product specs mid-sprint planning
Integration
- Vendor
- Onepage
- Category
- productivity
- Auth
- OAUTH2
- Tools
- 2
- Composio slug
onepage
Tools
- Search input post request
The searchinput endpoint allows users to perform a search query within the onepage platform. it accepts a required search string and optional parameters for language and output format customization. this endpoint is designed for retrieving
- Token details request
Retrieves detailed information about a specific token in the onepage system. this endpoint should be used when you need to obtain comprehensive data about a token, such as its associated permissions, expiration date, or other metadata. it's
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Onepage in the MCP directory and click Connect. 3. You'll be redirected to Onepage's OAuth consent screen — sign in with your Onepage account. 4. Grant read access to your workspace content and token metadata (Onepage requires both scopes for search and permission lookups). 5. After authorizing, Switchy redirects you back and confirms the connection. 6. Open any Space, type '@Onepage search [your query]' and send the message. 7. Onepage returns matching pages or documents inline. 8. To verify token details, use '@Onepage token details [token_id]' — useful for checking who can access a resource. 9. If search returns nothing, confirm your Onepage workspace has indexed content and your account has read permissions.
What teammates see: by default, memories from Onepage are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Find Onboarding Checklist
@Onepage search onboarding checklist. Return the most recent version and list the first five action items.Open in a Space →
Lookup PTO Policy
@Onepage search PTO policy. Summarize eligibility, accrual rates, and blackout dates in three bullet points.Open in a Space →
Check Token Permissions
@Onepage token details [token_id]. List the associated permissions and which user roles have access.Open in a Space →
Pull API Documentation
@Onepage search API authentication endpoints. Return the endpoint URL, required headers, and example request.Open in a Space →
Retrieve Brand Guidelines
@Onepage search brand guidelines logo usage. Summarize approved formats, minimum sizes, and prohibited alterations.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Onepage search for all meeting notes from last week that mention the Q1 roadmap
Found 4 items matching 'Q1 roadmap' from the past week: (1) 'Product Sync - Jan 15' containing roadmap timeline discussion, (2) 'Leadership Review' with budget allocation notes, (3) 'Engineering Standup' mentioning feature prioritization, and (4) 'Customer Success Debrief' referencing roadmap communication strategy. Each result includes the page title, creation date, and a snippet showing where your search term appears in context.
This example shows Onepage's search capability across your workspace content. The MCP returns structured results that the AI can synthesize into a readable summary. Note that search scope depends on your OAuth token's permissions — you'll only see pages and spaces you have access to in your Onepage account.
@Onepage what permissions does my current access token have and when does it expire?
Your Onepage access token has read and write permissions for the 'Product Team' and 'Engineering' spaces, plus read-only access to 'Company Wiki'. The token was issued on January 10, 2025, and expires on April 10, 2025 (89 days remaining). It includes the following scopes: pages.read, pages.write, search.execute, and tokens.inspect. No admin-level permissions are currently granted.
This token introspection example is useful for debugging access issues or auditing what the MCP can do on your behalf. The response helps you understand why certain operations might fail (missing scopes) or when you'll need to re-authenticate. This is a read-only query with no side effects.
@Onepage search our workspace for any pages mentioning 'API deprecation' and summarize the key dates and affected endpoints
Found 3 pages discussing API deprecation: The 'Engineering Changelog' page lists v1 endpoints being retired on March 1, 2025 (including /legacy/users and /legacy/posts). The 'Migration Guide' page outlines a transition plan with testing phases through February 15. The 'Support FAQ' page notes that customer notifications went out on December 20, 2024. All three pages emphasize that v2 equivalents are already available and recommend updating integrations before the cutoff date.
This example pairs Onepage's search with the AI's synthesis ability — the MCP retrieves raw page content, then the AI extracts and organizes the relevant information. This workflow is especially powerful for cross-referencing scattered documentation. Search results are limited by your token's space access and Onepage's rate limits (typically 100 requests per minute).
Use-case deep-dives
When Onepage works for small support teams searching internal docs
A 3-person support team fields 40 tickets a day and needs fast answers from product docs, runbooks, and past ticket resolutions stored in Onepage. The search MCP lets agents query the knowledge base from Switchy without tab-switching, which cuts median response time when the answer exists in docs. This works if your Onepage instance has under 5,000 pages and your team already uses OAuth for tool access. The trade-off: the search endpoint returns raw results with no ranking signal, so if your knowledge base is messy or has duplicate content, agents still spend time filtering. If you're already on Onepage and your docs are well-organized, connect this MCP and let your team search from the workspace where they draft replies.
Using Onepage MCP to surface onboarding materials for new hires
A 6-person startup onboards a new engineer every quarter and stores setup guides, architecture diagrams, and team norms in Onepage. The MCP's search tool lets the onboarding buddy pull relevant pages into Switchy during live pairing sessions, so the new hire sees the doc inline with the conversation. This is useful if your onboarding content lives in one Onepage workspace and you want to avoid sending 15 separate links. The limitation: with only 2 tools and no bulk-fetch capability, you're still doing one search at a time, which doesn't scale if onboarding spans 50 pages across multiple topics. If your onboarding is lightweight and doc-first, this MCP keeps the flow in one place without forcing the new hire to learn Onepage's UI on day one.
When Onepage MCP helps product teams prep standups with search
A 4-person product team runs a Monday sync where everyone shares progress against the roadmap, which lives in Onepage as a set of linked pages. The PM uses the search MCP to pull last week's updates and this week's milestones into Switchy 10 minutes before the meeting, so the team reviews context together instead of reading silently. This works if your roadmap is text-heavy and changes weekly, and if the PM is already comfortable with OAuth setup. The downside: the token-details tool doesn't add much here unless you're debugging permissions, so you're really paying for one search endpoint. If your sync is under 30 minutes and your roadmap is in Onepage, this MCP saves the PM from copy-pasting 6 pages into a doc every week.
Frequently asked
What does the Onepage MCP do in Switchy?
The Onepage MCP lets your team search across your Onepage workspace and retrieve token metadata directly from Switchy's AI interface. You can query documents, pages, or other content stored in Onepage without switching apps, and inspect token permissions when troubleshooting access issues. It's useful for teams that keep knowledge bases or project documentation in Onepage and want AI-assisted retrieval.
What OAuth permissions does the Onepage MCP request?
The MCP uses OAuth2 to connect, so you'll authorize it through Onepage's standard consent screen. The exact scopes depend on Onepage's API design, but typically include read access to your workspace content and token metadata. You don't need admin rights to connect your own account, but workspace-wide search may require elevated permissions depending on your Onepage plan.
Can the Onepage MCP create or edit pages?
No. The current toolset only supports searching content and retrieving token details. If you need to create, update, or delete pages in Onepage, you'll have to do that in the Onepage app directly or use their REST API outside of Switchy. This MCP is read-only by design.
Why use this instead of just opening Onepage in a browser?
The MCP brings Onepage search results into your AI conversation, so you can ask questions like "find the Q3 roadmap doc" and get inline answers without tab-switching. It's faster for quick lookups during a chat session, but you'll still need the Onepage UI for editing or visual layout work. Think of it as a shortcut, not a replacement.
Who on my team should connect the Onepage MCP?
Anyone who needs to reference Onepage content during AI sessions. Each person connects their own Onepage account via OAuth, so search results respect their individual permissions. If your team shares a single Onepage workspace, multiple people can connect the same MCP without conflicts. It doesn't consume extra seats or count against Onepage's user limits.