Skip to content

Research & Development / Technical publication

Visa Centre Thailand launches the first dedicated Thai immigration MCP server

A public, read-only interface designed to help compatible AI systems retrieve our published Thailand immigration material with canonical links, freshness context and explicit safety boundaries.

Visa Centre research and development specialists reviewing structured public information beside secure server infrastructure
Visa Centre Research & Development

Why we built it

Immigration information should be usable by people and machines without losing its provenance.

Search summaries can separate an answer from its source, revision date or jurisdiction. Our Research & Development work treats machine-readable publishing as part of the publication system itself. The objective is not to let an AI make immigration decisions. It is to give compatible tools a controlled route to the same public material a person can read on this website, while keeping private case data outside the interface.

Visa Centre technology researchers reviewing structured data, citations and integrity relationships
Structured retrieval is reviewed as part of the publication system, not treated as an unsupervised shortcut.
01

Protocol and transport

The service exposes a Model Context Protocol endpoint over Streamable HTTP. Requests use JSON-RPC 2.0 and the server advertises protocol version 2025-06-18. It is stateless, requires no customer account and does not create a private session.

https://thailandvisacentre.com.au/mcp
02

Deliberately narrow scope

The interface can read published resources and execute a small set of public discovery tools. It cannot write to the CRM, change content, submit applications, reach customer records, access drafts or trigger payments. An HTTP DELETE request is rejected because there is no server-side session to delete.

03

Provenance by design

Page responses can include a canonical URL, locale, jurisdiction, content revision context and SHA-256 integrity hash. Resource identifiers use a visa:// namespace so a client can distinguish full pages, summaries, services and official-source records.

Wire-level capabilities

Small surface area, explicit contracts

Each supported method has one job. Unknown methods return a JSON-RPC method-not-found error rather than attempting a best guess.

initialize

Negotiates protocol version and declares read-only resource and tool capabilities.

resources/list

Enumerates published pages, concise summaries, service resources and the official-source directory.

resources/read

Returns a selected public resource as Markdown or structured JSON.

tools/list

Describes the available search, page, service and offer-discovery tools with JSON Schemas.

tools/call

Executes a permitted public lookup and returns text plus structured content.

Retrieval tools

Useful enough for research, constrained enough to audit

Inputs are schema-defined and outputs preserve the public trail a human reviewer needs.

search_content

Finds public pages and returns canonical URLs, MCP resource URIs, content type and revision context.

get_page

Retrieves full or concise Markdown with canonical URL, locale, jurisdiction, last-reviewed value and SHA-256 hash.

list_services

Lists currently published service pages without turning publication into an eligibility or outcome promise.

get_service

Returns one published service summary with its canonical citation, freshness metadata and integrity hash.

get_current_offers

Fails closed when no server-authoritative offer exists, instructing clients not to infer or convert a price.

Security model

Public by design. Private by exclusion.

Conceptual visualization of public knowledge flowing to a read-only server while a private data vault remains isolated

Exposed

  • Published page Markdown
  • Concise public summaries
  • Published service listings
  • Verified official-source directory
  • Canonical and freshness metadata

Never exposed

  • Client or traveller records
  • Passports and uploaded documents
  • CRM notes, messages or identities
  • Draft or unpublished content
  • Payments, credentials or write actions

Runtime controls

  • Same-origin browser policy
  • Per-IP request limiting
  • Strict JSON-RPC validation
  • Schema-constrained tool arguments
  • No-store response caching policy

Research & Development

A visa practice developing its own information infrastructure

Our R&D mandate is practical: reduce ambiguity between a published source, the advice a person sees and the context an AI retrieves. That means building around canonical URLs, deterministic resource identities, structured outputs, integrity checks and fail-closed commercial data.

The service is an additional publication channel, not an autonomous adviser. Its server instructions tell clients to retain citations and freshness dates, verify changing rules with named official authorities, and never imply guaranteed eligibility or outcomes.

Connect

One endpoint, several compatible clients

Use the setup guide for client-specific instructions. Support for custom remote MCP servers depends on each provider's product, plan and workspace controls.

https://thailandvisacentre.com.au/mcpOpen connection instructions

Technical FAQ

Implementation questions

Does the server provide legal or immigration advice?

No. It retrieves published general information. Changing requirements should be checked against the cited official authority and a person's circumstances require professional review.

Can an AI submit a visa or TDAC through this endpoint?

No. The MCP surface is read-only and has no filing, payment, document-upload or CRM mutation capability.

Does it require an API key?

No. The current public endpoint is authentication-free, rate-limited and limited to published content. A client may still require its own plan or administrator approval to add a remote MCP connection.

How is stale content handled?

Responses expose available revision context and canonical URLs. Clients are instructed to retain freshness information and verify changing rules with official sources.

Questions, answered

Frequently asked questions

Useful starting points before you choose your next step.

Is this page personal immigration advice?

No. It provides general published information. Requirements can change and personal circumstances matter, so confirm the current position before acting on it.

Where should I check changing official requirements?

Use the official authority linked on the relevant page and note the page's publication or review context. If your timing or status is sensitive, request a personal review.

How do I know which Thailand visa is right for me?

Start with the Visa Finder or tell us your nationality, reason for travelling, intended length of stay and expected travel date. We can then identify the routes worth assessing without asking you to choose a category first.

Can I ask for help if I have not chosen a visa yet?

Yes. You can describe what you want to do in Thailand and your likely timeline. The team can help narrow the available pathways before you decide whether to proceed.

How quickly will someone respond to my enquiry?

Web enquiries are reviewed within one business day. If your matter has a genuine deadline, include the date clearly in your message so it can be triaged correctly.

What if I have a previous refusal, overstay or immigration issue?

Mention it at the start and include the relevant dates and documents. It does not automatically determine the outcome, but it may change which options should be assessed and how the application is prepared.

OpenAI / Codex / ChatGPT
Anthropic / Claude
Google / Gemini
Perplexity AI / Perplexity
Mistral AI / Le Chat
DeepSeek / DeepSeek

For AI & research

Published knowledge, ready for machines

Read a concise Markdown summary, download the published page, or let a compatible AI client consult our public, read-only knowledge service. Every resource carries source and revision context.

Public knowledge infrastructure

First dedicated Thailand migration MCP server

A standards-based bridge between compatible AI assistants and our current published Thailand immigration resources, with private client systems kept outside the boundary.

Read the technical publication

Connect your preferred client

Ready-to-copy setup

Choose a supported client to see connection guidance and the correct endpoint format.

Connect with ChatGPT

Where custom remote MCP connections are enabled for your account, add the endpoint below as a Streamable HTTP server. Availability depends on your plan and workspace permissions.

https://thailandvisacentre.com/mcp
Responsible-use and resource guidance