What You Need Before You Start
An active Juristat subscription with MCP/API access enabled
Access to Microsoft Copilot Studio (license or trial)
Microsoft 365 Copilot licenses for end users (if deploying to Copilot Chat, not just Teams)
Generative Orchestration enabled in your Copilot Studio environment (Settings > Generative AI > “Use generative AI orchestration for your agent's responses?” > Yes)
Admin permissions to create and publish agents
Table of Contents
Admin Setup (One-Time)
Reference
Don't have MCP enabled? Contact sales@juristat.com for more information
Running into errors or unexpected behavior? See the FAQ section at the bottom of this guide.
Admin Setup (One-Time)
Steps 1 through 9 are completed by your organization's Copilot Studio admin. This setup only needs to happen once. It creates the Juristat agent, connects it to the Juristat MCP server, and publishes it for your team.
Step 1: Request Credentials from Juristat
Before configuring anything in Microsoft, contact your Juristat account manager to request MCP integration credentials. Juristat will provide you with:
A Client ID
A Client Secret
The MCP endpoint URL
You will also need to send Juristat a Redirect URL later in this process (Step 5). The credential exchange only happens once. You will not need to repeat it unless credentials are rotated.
Step 2: Create an Agent in Copilot Studio
2a. Sign in to copilotstudio.microsoft.com. Go to the Agents page and click + Create blank agent in the top right of the page.
2b. Give your agent a name (e.g., "Juristat Patent Intelligence") and click Create.
Step 3: Configure the Agent
3a. Under "Select your agent's model," change the model to Claude Opus 4.6. Juristat recommends the latest version of Claude Opus (Sonnet is also acceptable).
3b. In the Description field, paste the following (Copilot's orchestrator uses this to decide when to invoke the agent):
Patent prosecution analytics powered by Juristat. Give it an application number, examiner name, company, or law firm and get data-driven examiner intelligence, office action response strategies, portfolio metrics, competitive comparisons, and technology landscape analysis. Built for patent attorneys, agents, and IP professionals.
3c. In the Instructions section, click Edit and paste the following instructions:
You are a patent prosecution analytics agent powered by the Juristat MCP server. Your users are patent attorneys, agents, paralegals, and IP managers. They are domain experts -- do not explain basic patent concepts unless asked.
Your job: Pull data from Juristat, synthesize it into actionable intelligence, and present it so the user can immediately act on it or share it with colleagues and clients. You are the analyst; they are the decision-maker.
Handling Juristat MCP response data:
Juristat MCP tool responses return structured JSON with three key sections you must parse and use:
results: The actual data (metrics rows, application records, etc.). This is what you synthesize into your analysis.
links: Contains analyticsLink (Juristat Intelligence dashboard), datasetLink (Juristat data table), and otherLinks (entity-specific pages for assignees, tech centers, examiners, art units, etc.). Always include analyticsLink in your response so the user can explore the full interactive view. When mentioning specific entities (e.g., "Apple" or "TC 2600"), match them against otherLinks[].text variants and hyperlink to the corresponding url.
notes: Contains interpretation notes like "Interpreting assignee search 'Apple' as 'Apple, Inc.'" Surface these so the user knows exactly which entity was matched.
Example: If the response contains otherLinks with {"text": ["Apple", "Apple, Inc."], "url": "https://app.juristat.com/assignee-at-disp/563/intelligence"}, and you mention Apple in your analysis, link to that URL. At the end of your analysis, include the analyticsLink as "Explore this analysis in Juristat: [link]."
CRITICAL - Juristat MCP tool calling rules:
When calling any Juristat MCP tool, you must use the exact parameter names and values defined in the tool schema. Do not paraphrase, expand abbreviations, or invent human-readable alternatives. If the schema says "avgOfficeActions", use "avgOfficeActions" -- not "averageOfficeActions". If the schema says "type-102", use "type-102" -- not "type_102" or "anticipation". Copy enum values character-for-character from the schema definition.
Entity filters (assignee, firm, examiner, techCenter, artUnit, cpcClass, status, filingDate, etc.) must always be nested inside the "filters" object for application tools or "applicationFilters" object for office action tools. Never place filter fields at the root level of the request.
Every tool has required parameters that must be included or the call will fail. For get-uspto-application-metrics, "metrics" is required and must be an array. A good default when the user does not specify exact metrics: ["allowanceRate", "avgOfficeActions", "avgMonthsToDisposition"]. For search-applications and search-office-actions, "search" is required and must be an object. For get-office-action, applicationNumber, documentCode, and mailroomDate are all required.
Core rules:
Always lead with the strategic insight, not a description of what you did. The first sentence of every response should be the takeaway.
Always call get-application-info first when given an application number. It gives you the examiner name, art unit, OA history, and document list you need for all subsequent calls.
Always call get-office-action-metrics with aggregateBy: responseType when building any prosecution strategy recommendation. This is the most strategically valuable data in the platform -- it tells you which response type (amendment, interview, RCE, appeal) has the highest win rate for the relevant examiner or art unit.
When Juristat MCP tool responses include links (publication PDF URLs, analytics dashboard URLs, or URLs embedded in HTML comments), always surface them in your response. Format them inline next to the relevant analysis: "View in Juristat: [URL]." These links let the user verify data against the live platform. Never silently drop links from tool responses.
Never fabricate data. If a tool does not return a specific metric, say so. Do not fill in from general knowledge. Your users make legal and business decisions based on what you report.
Never provide legal advice. Say "the data suggests" or "this examiner's history indicates," not "you should." You provide data-driven analysis; the attorney makes the legal judgment.
Flag small sample sizes. If a metric is based on fewer than 20 disposed applications, say so explicitly. Do not present thin data with the same confidence as robust data.
Use tables for comparative data (examiner vs. art unit, firm vs. firm, year-over-year). Use prose for strategic recommendations and risk assessments. Never dump a table without a sentence explaining what to look for.
When listing applications, apply a publicationDate filter to avoid very recently filed applications with incomplete data.
Stay in scope. If asked to draft claims, write amendments, or do legal drafting work, explain that your expertise is prosecution analytics and strategy, and offer what you can do (pull examiner data, read OA text, recommend strategy).
Step 4: Add the Juristat MCP Server
4a. Click Tools in the top navigation bar, then click + Add a tool. Select New tool, then select Model Context Protocol.
4b. In the "Add a Model Context Protocol server" dialog, fill in the following:
Server name: Juristat
Server description: Juristat patent intelligence: examiner analytics, application search, office action analysis, and prosecution metrics for USPTO patent data.
Server URL:
https://mcp.prod.public.juristat.com/mcpAuthentication: Select OAuth 2.0
4c. After selecting OAuth 2.0, select Manual as the type and enter the following:
Client ID: (provided by Juristat in Step 1)
Client Secret: (provided by Juristat in Step 1)
Authorization URL:
https://login.juristat.com/authorizeToken URL template:
https://login.juristat.com/oauth/tokenRefresh URL:
https://login.juristat.com/oauth/tokenScopes:
openid profile email offline_access legacy:CAN_USE_PLATFORM_SEARCH_SCOPES mcp:agent:all mcp:analytics:all mcp:export:all mcp:report:all mcp:search:all use:juristat view:appealsClick Create.
Step 5: Register the Redirect URL
5a. After clicking Create, you will see a success message: "Your tool was created successfully!" This page displays a Redirect URL. Copy this URL.
Important: Do not close or cancel this wizard. Closing the wizard will lose your progress and you will need to start over from Step 4.
5b. Send the Redirect URL to your Juristat account manager (or email support@juristat.com). Juristat will register this URL in the authentication system. Please allow up to one business day for this to be processed. Juristat will confirm when it is ready.
5c. Once you receive confirmation from Juristat, return to the wizard in Copilot Studio and click Next.
Step 6: Create the Connection
6a. On the "Add tool" page, you will see the Juristat server with a Connection status of "Not connected." Click the Connection dropdown and select Create new connection.
6b. A "Connect to Juristat" dialog appears. Click Create.
6c. A sign-in window will appear. Sign in with your Juristat credentials.
6d. After signing in, the connection status will show a green indicator. Click Add and configure to finish adding the tool to your agent.
Step 7: Test the Connection
7a. Click Test in the top right of Copilot Studio to open the test chat panel.
7b. Try a query to confirm the connection is working. For example:
"Get me the examiner report for art unit 2100."
"Search for recent published patent applications from Microsoft."
"Summarize patent application 12000005."
If the agent returns results, the connection is working.
If you see an authentication error, confirm with Juristat that the Redirect URL from Step 5 has been registered.
Step 8: Publish to Microsoft 365 Copilot and Teams
Copilot Studio is the admin tool where you build and manage agents. To make the agent available to your team, you need to publish it to Microsoft 365 Copilot and/or Teams.
8a. Click Channels in the top navigation bar. Click Microsoft 365 Copilot and Microsoft Teams.
8b. Make sure "Make agent available in Microsoft 365 Copilot" is checked. Click Add channel.
8c. A "Ready to publish?" dialog appears. Click Publish.
Step 9: Share with Your Team
9a. After publishing, click Availability options right under Juristat MCP Demo under the agent preview on the Channels page.
9b. Choose who should have access to the agent. You can share with specific users or with everyone in your organization. Make sure "Viewer" (Can chat with this agent) is selected.
9c. Click Update, then click Publish one more time to apply the updated sharing settings.
To share with users, you can also:
Copy the install link from Availability options and send it to users
Add the agent to the Teams app store so shared users can find and install it
Submit for admin approval via the Teams or Microsoft 365 Admin Center for organization-wide access
Troubleshooting
"Oops, something went wrong" / Callback URL mismatch This error appears when you try to create a connection before Juristat has registered your Redirect URL. Send the URL from Step 5 to Juristat and wait for confirmation before trying again. Do not close the wizard while waiting.
Agent does not appear in Microsoft 365 Copilot After publishing, there can be a short delay before the agent shows up in the Agent Store. If it still does not appear after 15-20 minutes, go back to Copilot Studio, verify the Microsoft 365 channel is added, and publish again.
Connection fails after setup Make sure you are using the correct Juristat login credentials. If the issue persists, contact Juristat support.
Need hands-on help with configuration? If your Copilot admin wants to walk through the setup or troubleshoot errors together, the Juristat product team is happy to hop on a call. Reach out to your account manager or email support@juristat.com to schedule.
FAQ
1. What does "Sorry, something unexpected happened" or "SystemError" mean?
These errors come from Copilot, not Juristat. They happen when Copilot sends an incorrectly formatted request to the Juristat server or gives up mid-process. The agent instructions in Step 3 are designed to prevent this. Make sure the full instructions are pasted into your agent. If errors persist after adding them, contact Juristat support.
2. Why does the agent take a long time to respond?
Complex queries can take 1 to 3 minutes to process. This is normal. If the agent does not respond at all after several minutes, try starting a new chat and simplifying your prompt.
3. Can I pull data across a large batch of applications at once?
Batch queries (e.g., "get the first independent claim from each of these 20 applications") can overwhelm Copilot's processing capacity because each application returns a large amount of data. For batch workflows, use the metrics and search tools instead (e.g., "search for allowed applications in Tech Center 2800 matching 'echo curve amplitude'"). These return summary-level data that Copilot can handle. For detailed per-application data, query applications one at a time.
4. Are the agent instructions in Step 3 required?
Yes. Without them, Copilot is much more likely to make errors when calling Juristat tools. If your agent was set up without these instructions, add them.
5. Tips for getting better results:
Start with a specific application number, examiner name, or company name
Ask one question at a time
If a query fails, rephrase it or break it into steps
For complex analysis, build up context across multiple prompts rather than asking for everything at once
Going Further
Copilot Studio supports more advanced configurations beyond this basic setup. You can build multi-step conversation flows that chain Juristat tools together, combine Juristat with other MCP servers or Power Automate flows, and deploy the agent to additional channels like SharePoint. These setups may require more hands-on Copilot Studio experience. Your Juristat account team can help scope and advise.
Support
Resource | Link |
Juristat Support | support@juristat.com or your account manager |
Copilot Studio Docs | |
MCP in Copilot Studio |